Show "stopping" in progress bar
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.7k
- Forks
- 2k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 80
Description
Is your feature request related to a problem? Please describe.
Interruptibility is getting better, but we'll inevitably have cases where new code is not doing this well, or perhaps a plugin takes its time, etc.
When a process does not respond, users quickly start to question
- whether Nix is broken
- whether the SSH connection was lost
- whether their system froze
- whether their sanity was lost (maybe this one is just me)
This includes responding to interruption, in which case users are already aggravated.
Describe the solution you'd like
Be communicative. Immediately show that Nix is stopping.
After hitting Ctrl+C, immediately update the progress bar to show something (STOPPING), along with the existing content, to show what is/was happening while they're waiting.
Describe alternatives you've considered
"Just fix interruption" - not a sufficient solution, as described. Perfect enemy good, etc.
Additional context
Priorities
Add 👍 to issues you find important.
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 locating Nix's progress-bar implementation and the Ctrl+C interruption handling described in the issue. Verify that the display immediately includes "STOPPING" while retaining its existing content, then exercise an interruptible operation to confirm the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100