-
Notifications
You must be signed in to change notification settings - Fork 741
Clarify the ambiguous process-level CryptoProvider error #2558
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2558 +/- ##
=======================================
Coverage 95.35% 95.35%
=======================================
Files 97 97
Lines 21460 21464 +4
=======================================
+ Hits 20463 20467 +4
Misses 997 997 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
This makes sense to me, thanks!
I think we should backport this to rel-0.23
.
Benchmark resultsInstruction countsSignificant differencesClick to expand
Other differencesClick to expand
Wall-timeSignificant differencesThere are no significant wall-time differences Other differencesClick to expand
Additional informationCheckout details:
|
Sounds good, let me know if there's anything I need to do to make that happen. Should I rebase on that branch? |
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.
Thanks!
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.
Thanks 👍
Thanks for the offer. I went ahead and opened the backport PR to make life easy: #2561 |
I have personally hit this error after adding a new dependency that enabled the
ring
feature without me realizing.I think the instruction of the error, to call
CryptoProvider::install_default()
, does not help the user understand why this error suddenly appeared.Yesterday I saw this reddit thread hit the same problem, so lets fix this. I'm open to different wording than I came up with, I'm not an expert on this crate.
This is how the new error appears: