Make "skipping nightly which is missing installed component" more prominent
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Describe the problem you are trying to solve
When only looking at the final summary printed by rustup, one cannot tell that a nightly was skipped due to missing components:
stable-x86_64-unknown-linux-gnu unchanged - rustc 1.51.0 (2fd73fabe 2021-03-23)
nightly-x86_64-unknown-linux-gnu updated - rustc 1.53.0-nightly (42816d61e 2021-04-24) (from rustc 1.53.0-nightly (132b4e5d1 2021-04-13))
Describe the solution you'd like
It would be nice to add some indication to the summary that the latest nightly installed is not the latest nightly, due to missing components. For example:
nightly-x86_64-unknown-linux-gnu updated - rustc 1.53.0-nightly (42816d61e 2021-04-24) (from rustc 1.53.0-nightly (132b4e5d1 2021-04-13)) (not updated to '42816d61e 2021-04-25' because of missing installed component 'rustfmt')
This is quite a long line though; maybe there are better ways.
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 the rustup update summary output and the path that skips a nightly when an installed component is missing. Review the existing summary and missing-component handling before deciding how they connect. Done means the final summary clearly indicates that the latest nightly was not installed and identifies the missing component, with coverage for this case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100