curl needs `--retry-all-errors`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Verification
- I searched for recent similar issues at https://github.com/rust-lang/rustup/issues?q=is%3Aissue+is%3Aopen%2Cclosed and found no duplicates.
- I am on the latest version of Rustup according to https://github.com/rust-lang/rustup/tags and am still able to reproduce my issue.
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
- use rustup, then switch between wifi connections.
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)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start by locating rustup's curl download path and checking how retry behavior is configured; done means transient connection resets while switching networks are retried without changing unrelated failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100