-
Notifications
You must be signed in to change notification settings - Fork 513
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
Multiple issues in the 0.7.3 release #1597
Comments
@shaangill025 and @andrewwhitehead --- can the two of you please look at these? Shaanjot likely the 1, 2 and 3 as they are in the same area, Andrew the fourth because of the Askar connection. Thanks |
For #4, it appears that the process is failing when trying to update the credential exchange record because it doesn't exist. This could be because auto-respond was enabled and the exchange has already completed and been removed. I can't see why this behaviour would be any different with the Askar backend. |
It's indeed different. I have two 0.7.3 agents, one running in indy the other in aksar, both have all auto-respond-credential-xxx flags set to false. The indy one works a s expected. The askar one receives the credential offer, but is not able to handle the credential request trigger because the record is missing. I double checked to see if maybe the exchange runs through automatically and the controller reacts on a wrong state, but thats not the case. |
@etschelp Which Storage Backend are you running in the Acapy. Do you use Postgres or SQLite ? |
Always Postgres |
@etschelp We saw also errors on the Postgres Backend regarding encoding problems with |
What are your encoding problems? So far I did not experience any. But your question made me curious, by looking at the init methods in the indy and askar sdk's I do not see that there is any encoding set. Which means for postgres it comes back to the defaults. If you are using the docker image its derived from |
Askar (via sqlx) always sets the client encoding to utf8 when creating a connection. What kind of encoding problems are you seeing? |
On my Mac I can run the performance demo with a test of 300 credential exchanges using the following (with Postgres.app installed): Startup duration: 5.05s
Faber | Connected
Connect duration: 0.17s
Faber | Publishing test schema
Alice | Connected
Faber | Schema ID: VYRv5TfbgWBuuzru4ayZkb:2:degree schema:42.9.95
Faber | Publishing test credential definition
Faber | Credential Definition ID: VYRv5TfbgWBuuzru4ayZkb:3:CL:131901:default
Publish duration: 5.73s
Faber | Started 100 credential exchanges in 2.10s
Faber | Started 100 credential exchanges in 3.75s
Faber | Done starting 300 credential exchanges in 9.38s
Issuing credentials 100.0% [===================================================>] 300/300 eta [00:00]
Receiving credentials 100.0% [===================================================>] 300/300 eta [00:00]
Faber | Completed 300 credential exchanges in 10.68s
Faber | Average time per credential: 0.04s (28.09/s)
Alice | alice602305 DB | items | items_tags
Alice | ==========================================================================================
Alice | 300 creds | 908 6568kB | 3914 848kB
Alice |
Faber | faber446483 DB | items | items_tags
Faber | ==========================================================================================
Faber | 300 creds | 19 72kB | 45 72kB |
@andrewwhitehead @etschelp We fixed by setting the |
Can we get an update on this one at the ACA-Pug meeting today/tomorrow (2022.02.08)? We have a WIP PR and some back and forth that may address some of the issue. Ideally, I'd like to get the issues remaining separated into separate issues, because who doesn't like having more issues? 😂 It is easier to track one issue per issue. |
I'm using this ticket to collect issues that I found in the 0.7.3 release.
1. Tails file upload fails when a credDef is created and multi ledger support is enabled.
See discussion on the chat: https://chat.hyperledger.org/channel/aries-cloudagent-python?msg=XodRcp7dFxmncAWma I still do not get this to work.
2. Revocation notification has a wrong revocation id for V1 exchanges (V2 works as expected)
For example the credential acked event has the following link to the revocation registry:
But in the revocation event the value of the revocation id becomes 6 instead of 5.
3a. V2 Credential exchange ignores the auto-respond-credential-request: false flag
If aca-py receives a V2 credential request it immediately responds even if the auto flag is set to false. Works as expected for V1.
3b. V2 Presentation exchange ignores the auto-respond-presentation-proposal: true flag
If aca-py receives a V2 presentation proposal and the auto respond flag is set to true aca-py does not automatically respond. Works a expected for V1.
4. Wallet type askar has issues when receiving V1 credentials.
Probably same as or related to #1588 Any other time answering a credential offer with a request fails with:
The text was updated successfully, but these errors were encountered: