task retry count doesn't work if `extras.gangAllocation` is not set to false
Open
Nobody has claimed this yet.
pai-dev
- Dominant language
- JavaScript
- Stars
- 2.7k
- Forks
- 554
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 14
Description
Currently, if we only set task retry count (like the following picture), but doesn't modify extras.gangAllocation, the setting won't work.
Users may easily get confused by the behavior. Could we pop out a warning to remind the user to set extras.gangAllocation?
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 from the task configuration UI where retry count and extras.gangAllocation are set. Reproduce the configuration with a retry count and no explicit gangAllocation value, then trace the existing validation or warning behavior. Done means users receive a clear warning to set extras.gangAllocation when this combination is used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100