-
Notifications
You must be signed in to change notification settings - Fork 519
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
1.2 LTS: Askar upgrade and fix profile unique names #3477
1.2 LTS: Askar upgrade and fix profile unique names #3477
Conversation
Signed-off-by: Daniel Bluhm <dbluhm@pm.me>
Signed-off-by: Daniel Bluhm <dbluhm@pm.me>
Signed-off-by: jamshale <jamiehalebc@gmail.com>
Waiting for another askar library fix... |
Signed-off-by: jamshale <jamiehalebc@gmail.com>
|
Just confirming, this isn't out in a release yet, right? |
I'm not sure why this one didn't create a release. Not exactly sure what to do. I think create a tag and then run the publish workflow for it? The 0.12.lts was released properly. |
I didn't do anything for the 0.12.lts so I'll see if @swcurran knows what happened or I can try and get it released later today. |
My screw-up. I just didn’t create the release after the merge. The date is a bit messed up, but so be it. |
@dbluhm version 1.2.2 is available now. |
A PR to enable a patch release to upgrade Askar to 0.4.3 and fixes a problem with wallet names in a multitenant, single-wallet configuration.
Addresses the problem outlined in #3471 around profiles in the multi-tenant/single wallet configuration. The update to Askar address an intermittent hang on startup, and a dependency change that can result in a substantial performance improvement in some cases. See issues: openwallet-foundation/askar#350, openwallet-foundation/askar#351, openwallet-foundation/askar#354. This comment on one of the PRs describes the scenario where a substantial performance improvement was seen as a result of the change in Askar.