there should be a "stopping" status
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
Generally: There should be a status for "stopping" an allocation.
This screenshot shows the job UI after I reduced the count of a group from 3 to 2.
This allocation is definitely not "starting".
The topology UI shows the same thing:
A minute later - it's gone.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the allocation count reduction shown in the job UI and cluster topology UI, then trace how the allocation status is presented while the stopped allocation is being removed. Done means both views distinguish a stopping allocation from a starting one before it disappears; the issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100