Default to `stable` when no active toolchain is present
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Problem
having cargo and rustup installed and call it first time it errors out, the only action i did not expect when building something. if you can print "run a command to choose stable" then really the software can choose a reasonable default by itself please. " you did not specify, so i chose ... for you".
❯ cargo build -p daemon --bin kanidmd --release
error: rustup could not choose a version of cargo to run, because one wasn't specified explicitly, and no default is configured.
help: run 'rustup default stable' to download the latest stable release of Rust and set it as your default toolchain.
Steps
No response
Possible Solution(s)
No response
Notes
No response
Version
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 rustup's toolchain selection when cargo build runs with no configured default. Review how the existing error and rustup default stable guidance are produced, then identify the relevant tests for this case. Done means an unconfigured installation selects stable or otherwise reflects an agreed defaulting behavior, with tests covering the first build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100