-
Notifications
You must be signed in to change notification settings - Fork 232
[cache] repair
fails with "No source of cryptographically secure random numbers available"
#4585
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
Comments
A valid log with the exact issue is previously reported in another issue: #4584 |
Thanks for reporting. I guess we could limit the amount of packages we repair concurrently around: pub/lib/src/source/hosted.dart Line 1310 in 59406fa
But in the bigger picture I think we should deprecate/remove A command that would instead re-download all package-versions of the "current pubspec.lock" that would make a lot of sense. @jonasfj WDYT? |
As a workaround I think the best approach currently is to do |
Repairing packages under specific projects sounds meaningful. The |
Good point. We should also have a specific command for that. (Or find a better way of handling globally installed packages: #4313) |
Uh oh!
There was an error while loading. Please reload this page.
Environment
Dart: 3.8.0
Flutter: 3.32.0
Problem
When running
flutter pub cache repair
, after a while of resetting, the process starts to throw:Expected behavior
Repairing should proceed without exceptions. Try adding a mutex lock when repairing a batch of packages.
Logs
The text was updated successfully, but these errors were encountered: