More useful error message for unsupported platforms
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Trying to use rustup on an unsupported platform leaves the user with what looks like a temporary failure:
curl https://sh.rustup.rs -sSf | sh
info: downloading installer
curl: (22) The requested URL returned error: 404 Not Found
rustup: command failed: curl -sSfL https://static.rust-lang.org/rustup/dist/arm-unknown-freebsd/rustup-init -o /tmp/tmp.B6K8gOHq/rustup-init
Ideally static.rust-lang should detect that a host triplet was selected that is known but currently not supported and return a status code that rustup understands. Unknown triplets would cause a 404.
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
Start by tracing how rustup handles the installer download failure and how the rustup-init host triplet is selected. Review the interaction with static.rust-lang for known-but-unsupported versus unknown triplets; done means unsupported platforms produce a distinct status that rustup turns into a useful error, while unknown triplets still return 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100