Simplify CompletionPolicy for common users
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
User easy to misconfig job CompletionPolicy, such as:
taskRoles:
taskrole:
instances: 1500
completion:
minFailedInstances: 500
minSucceededInstances: 500
We may need to simplify this and guide user to set it correctly, such as:
- We could produce a warning for this kind of jobs. minFailedInstances and minSucceededInstances are much smaller than "instances"
- We can also provide several common policies, such as minfail = 1, minsucc = instances, etc, so most user can directly select one of them, and for advance users they can still specify these specific numbers.
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
The issue names CompletionPolicy and the taskRoles completion configuration, but it does not identify files, tests, or a specific implementation path. Start by locating those definitions and the job-configuration handling, then clarify whether the intended outcome is validation warnings, preset policies, or both before defining completion criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100