-
Notifications
You must be signed in to change notification settings - Fork 516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: handle stored afgo and findy docs in corrections #2450
fix: handle stored afgo and findy docs in corrections #2450
Conversation
Signed-off-by: Daniel Bluhm <[email protected]>
Signed-off-by: Daniel Bluhm <[email protected]>
Ran through with AATH and the AF-Go test now runs (yay!), but the Findy Agent test still hangs on the test ping. Not sure if the behaviour has changed. Attached are the logs from the run. |
Signed-off-by: Daniel Bluhm <[email protected]>
Kudos, SonarCloud Quality Gate passed! |
@swcurran most recent commit should take care of that. Issue was caused by receiving a |
Worked! Nice — thanks. |
Nightly artifact generated that can be used for testing if anyone has time. @WadeBarnes , if you have time to deploy for IDIM, that would be good. I can do a final 0.10.0 tag later today/tonight. Any other tests would be appreciated! |
The new Nightly image has been deployed to IDIM |
This PR should fix ACA-Py <-> AFGo interop by correcting a case where the LegacyPeerDIDResolver was not properly dereferencing the recipient keys for the DIDComm service.
Specifically, it should fix this error:
This PR also fixes an error where docs that didn't have a proper did url for the ID of the service (like those received from findy) are corrected before used. For example:
Fixes #2449