-
Notifications
You must be signed in to change notification settings - Fork 214
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
Add retries for package installations #1994
Comments
To be sure, this is upon The retry client does only retry on certain network errors (e.g. 50x I think). It could be that certain network errors aren't retried because it assumes something bigger is faulty :D |
Yes, this is happening during |
Is there any way to see retroactively if pixi retried or not? Maybe it might makes sense if pixi wrote a warning to stderr 🤔 |
This is the one we're using: https://docs.rs/reqwest-retry/latest/reqwest_retry/ I do think we can customize the function in order to add logging. |
From what I can see, So it seems to me that it doesn't retry for the issues that I have 🤔 |
@baszalmstra was conda/rattler#837 in any way related to this issue? |
we experience these issues with pixi 0.28.0, haven't tried newer pixi versions yet... i'll check 0.29.0 in the coming days |
So i tried it out with 0.29.0 and the errors are still there unfortunately. Since i didn't see any warning messages (which should be included in the default log level, right?) I'm assuming that pixi is still not retrying on these errors 🤔 |
i got some debug logs with
the whole ci run failed within 10s; what do you think to do non-concurrent retries? |
also @baszalmstra do you think we could make https://github.com/conda/rattler/blob/b44887563c20aa9973da39b7a01eb72c37e09d91/crates/rattler_package_streaming/src/lib.rs#L27-L28 more informative? |
Problem description
In fragile networks with higher package loss, we often run into issues like the following:
or
This is most likely due to networking issues on the first download.
It would be nice if pixi tried multiple times and only fail after the 5th time or so. Maybe also configurable in the global config?
The text was updated successfully, but these errors were encountered: