jamshale
jamshale
I haven't tried to debug it yet but these failing tests are trying to use the `/ledger/register-nym` endpoint via the `register_did` method in `demo/runners/support/agent.py` and getting a 400 error.
Updating via https://github.com/hyperledger/aries-cloudagent-python/pull/3008
Updating via https://github.com/hyperledger/aries-cloudagent-python/pull/3008
Updating via https://github.com/hyperledger/aries-cloudagent-python/pull/3008
Updating via https://github.com/hyperledger/aries-cloudagent-python/pull/3008
Updating via https://github.com/hyperledger/aries-cloudagent-python/pull/3008
Updating via https://github.com/hyperledger/aries-cloudagent-python/pull/3008
Will upgrade via https://github.com/hyperledger/aries-cloudagent-python/pull/3004
Hmm. Might have messed something up with that ` Tests / Test Python 3.9 Expected — Waiting for status to be reported ` I think it could just be changed...
> A few questions, and a suggestion. > > Is it necessary to run the sonar scan on the PR and on the merge? Just wondering what the difference is...