-
Notifications
You must be signed in to change notification settings - Fork 892
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
curl needs --retry-all-errors
#4062
Comments
@lolbinarycat Thanks for filing this issue! However, I am not quite sure whether you referring to the In other words, would you mind explaining more about when you usually encounter this error? Many thanks in advance 🙇♀ |
(Not original reporter, but am impacted) Both could use some retry logic (I've had the problem in both phases, and the fact that neither handles it gracefully doesn't help the user understand what to do), bu for me the biggest pain point is the The Veilid CI system has a higher than 25% rate of failure over the past months building nightly packages because of this issue. Output pasted:
|
Verification
Problem
"Connection Reset By Peer" is by-default treated as a fatal error by curl, but can be produced spuriously, either due to switching networks, or overly aggressive load-balancing by ISPs.
Steps
Possible Solution(s)
No response
Notes
No response
Rustup version
rustup 1.26.0 (1980-01-01)
Installed toolchains
Default host: x86_64-unknown-linux-gnu
rustup home: /home/binarycat/.rustup
installed toolchains
nightly-2024-06-10-x86_64-unknown-linux-gnu
nightly-x86_64-unknown-linux-gnu (default)
stage1
1.80.1-x86_64-unknown-linux-gnu
active toolchain
nightly-x86_64-unknown-linux-gnu (default)
rustc 1.83.0-nightly (2bd1e894e 2024-09-26)
OS version
NixOS 24.05 (Uakari)
The text was updated successfully, but these errors were encountered: