Wade Barnes

icon indicating a website link https://ca.linkedin.com/in/wwjbarnes icon indicating an email [email protected]

icon company Neoteric Technologies Inc. icon location Qualicum Beach, BC, Canada icon location Software Architect/Developer, Site Reliability Engineer, Contributing member of the Exchange Lab and BCDevExchange community, Open Source Contributor

Results 404 comments of Wade Barnes

Support macOS and windows binaries in the release

Hey @tplooker, We're specifically looking to be able to include the `ursa-bbs-signatures` package in multiarchitecture `ACA-py` images supporting `linux/arm64` and `linux/386`. Currently the `ursa-bbs-signatures` will only install successfully on a...

🐛[Bug] - When running in multi-ledger configuration, a read-only agent will fail to start unless it's "main" ledger has a TAA

> **For context:** this error surfaced when turning off the TAA on CANdy/BCovrin ledgers and attempting to run VC-AuthN (which uses ACA-Py in read-only mode) with a ledger configuration specifying...

🐛[Bug] - When running in multi-ledger configuration, a read-only agent will fail to start unless it's "main" ledger has a TAA

Which version of ACA-Py was being used? Did you try the same procedure with a previous version of ACA-Py for comparison?

🐛[Bug] - When running in multi-ledger configuration, a read-only agent will fail to start unless it's "main" ledger has a TAA

No issues were found when testing with ACA-Py v0.10.3 agents direct connected to (not using ledgers.yml) BCovrin-Test, CANdy-Test and Sovrin TestNet. `ACAPY_READ_ONLY_LEDGER=false` in all cases. - `askar` secure storage

🐛[Bug] - When running in multi-ledger configuration, a read-only agent will fail to start unless it's "main" ledger has a TAA

No issues were found when testing with ACA-Py v0.7.4 with an agent using a ledgers.yml file listing BCovrin-Test, CANdy-Test and Sovrin TestNet, and using Sovrin TestNet as the production (write)...

🐛[Bug] - When running in multi-ledger configuration, a read-only agent will fail to start unless it's "main" ledger has a TAA

No issues were found when testing with ACA-Py v0.7.4 with an agent using a ledgers.yml file listing BCovrin-Test, CANdy-Test and Sovrin TestNet, and using CANd-Test as the production (write) ledger...

🐛[Bug] - When running in multi-ledger configuration, a read-only agent will fail to start unless it's "main" ledger has a TAA

> No issues were found when testing with ACA-Py v0.7.4 with an agent using a ledgers.yml file listing BCovrin-Test, CANdy-Test and Sovrin TestNet, and using CANd-Test as the production (write)...

🐛[Bug] - When running in multi-ledger configuration, a read-only agent will fail to start unless it's "main" ledger has a TAA

> No issues were found when testing with ACA-Py v0.7.4 with an agent using a ledgers.yml file listing BCovrin-Test, CANdy-Test and Sovrin TestNet, and using CANd-Test as the production (write)...

🐛[Bug] - When running in multi-ledger configuration, a read-only agent will fail to start unless it's "main" ledger has a TAA

Odd, I tried starting up vc-authn locally with ACA-Py v0.10.3 and got the reported error. However the issue does not seem to affect existing agent deployments.

🐛[Bug] - When running in multi-ledger configuration, a read-only agent will fail to start unless it's "main" ledger has a TAA

Same issue with ACA-Py v0.7.4. Issues occur with `askar` and `indy` storage.