rustup warns about its own environment? ("warning: default toolchain implicitly overridden")
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Downstream issue: https://github.com/nabijaczleweli/cargo-update/issues/337
cargo-update (.../cargo-install-update) runs cargo install to install stuff, so the call-stack is (1) cargo install-update ... -> (2) cargo-install-update -> (3) cargo install. It appears that the rustup cargo wrapper puts the toolchain selected in 1 in the environment so lower layers will obey this configuration (good), understands and obeys it in 3 (good), but now decides to warn about this everything-going-as-designed scenario (bad).
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 reproducing the call chain described here: cargo install-update invokes cargo-install-update, which invokes cargo install through the rustup cargo wrapper. Trace how the selected toolchain is passed through the environment and when the warning is emitted. Done means this intended nested invocation still obeys the selected toolchain without producing the misleading warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100