-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
HTTP/2 stream errors aren't considered spurious network failures #6788
Comments
I've taken a brief look at this and would submit a PR. Does the relevant curl error just need to be added to this set of conditions (https://github.com/rust-lang/cargo/blob/master/src/cargo/util/network.rs#L48-L52)? What testing needs to be done for this change? For what it's worth the existing curl errors don't seem to have unit tests. If I can easily create a It looks like this curl error isn't in |
Next steps:
|
…alexcrichton Treat HTTP/2 stream errors as spurious network errors. Closes #6788.
I am running nightly builds of rust and seem to be having this issue again. Did something cause a regression. :( |
@Ancient123 What is the exact output from Cargo? What platform are you on? Are you using a system-linked version of libcurl? If so, which version? |
and similar for different crates at random. EDIT - This exact image/hash/digest: |
Seen recently in comments on rust-lang#6788
Thanks @Ancient123! I've added that code as a whitelist for a spurious error on #8102 |
Whitelist another known spurious curl error Seen recently in comments on #6788
First discovered in these logs, it looks like Cargo isn't correctly detecting a spurious network failure:
That's one that Cargo should automatically restart and attempt to redownload!
The text was updated successfully, but these errors were encountered: