Job state no longer change to Stopping immediately after click stop button on job detail page
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.7k
- Forks
- 554
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 14
Description
Organization Name:
Short summary about the issue/question:
Job state no longer change to Stopping immediately after click stop button on job detail page.
So user does not know if he has submit the stop request successfully, so no need to click stop button again.
Brief what process you are following:
- Submit a larger scale job with 700 tasks.
- Click stop button on job detail page
- Job state continue to be Running after a while (~30s)
How to reproduce it:
OpenPAI Environment:
- OpenPAI version:
- Cloud provider or hardware configuration:
- OS (e.g. from /etc/os-release):
- Kernel (e.g.
uname -a): - Hardware (e.g. core number, memory size, storage size, GPU type etc.):
- Others:
Anything else we need to know:
Contributor guide
No contributing guide indexed for this repository
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 stop-button flow on the job detail page with a larger job of about 700 tasks, then trace how the page receives and displays job-state updates after the stop request. Done means the state changes to Stopping immediately after one click, so users do not need to submit the request again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100