-
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: RevRegEntry Transaction Endorsement #2558
Conversation
shaangill025
commented
Oct 19, 2023
- resolve Possible endorsement processing bug -- RevRegEntry transaction not being signed #2441
Signed-off-by: Shaanjot Gill <[email protected]>
) | ||
except StorageNotFoundError: | ||
raise RevocationManagerError( | ||
f"No connection record found for id: {connection_id}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this checking to see if there is an endorser connection? Is so, the error message should be more explicit, I think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, to check that the connection_id
if provided when calling POST /revocation/revoke
exists. If no connection_id
is provided and the profile is author role then connection_id will be retrieved from endorser.endorser_alias
which will always exist. Maybe I can change it to No endorser connection record ....
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do these changes also account for the scenario where the revocation entry is not published contextually to the call to the /revocation/revoke
endpoint, but rather using the /revocation/publish-revocations
endpoint to publish in bulk?
Signed-off-by: Shaanjot Gill <[email protected]>
Thanks for pointing this out, now it does. |
Not for this issue, but doesn’t the “revoke and publish” and the “publish” endpoints use a common “publish” method? I would think they would... |
|
Signed-off-by: Shaanjot Gill <[email protected]>
Any word on when we can look at getting the failing tests resolved? |
@shaangill025 is looking into them, I'm following-up today to see where we are at |
It looks like the new unit tests were written before rebasing on some changes to the test framework. The fix seems to be just renaming 'async_mock' to 'mock' in test_manager.py. |
In the integration test it looks like Acme receives a notification that their credential was revoked, but when checking the status it hasn't been updated yet. Could be a timing issue or an unpublished update? |
Which is definitely related to the code being changed. |
Signed-off-by: Shaanjot Gill <[email protected]>
That's what I was wondering. It looks like the workflow was re-run and now only 1 scenario is failing, which seems to be a good candidate for timing issues (but I admit I have not had a chance to look into the test code yet to be 100% sure). |
Signed-off-by: Shaanjot Gill <[email protected]>
Signed-off-by: Shaanjot Gill <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good to me. If @dbluhm can take a peek and confirm I did not miss anything I think it's good to go 👍🏻
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not thrilled about the continued propagation of endorser_conn_id
and write_ledger
through several interfaces but I think that's unavoidable until we have endorser support behind the ledger agnostic AnonCreds interface. LGTM.
Do we want to try to get this out in a patch release separate from the AnonCreds-RS changes being made on main (in addition to merging this to main)? |
Yes, I think this was the strategy we decided to go with. Re-poinintg this to the |
Kudos, SonarCloud Quality Gate passed! |