Reject runs that have resource requests that cannot be satisfied.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 74
- Forks
- 23
- Avg merge
- 6d 16h
- Merged PRs (30d)
- 7
Description
Return an error when attempting to create a run with resource requests that the node pools will not (even) be able to satisfy, instead of the runs remaining in a pending state indefinitely.
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 at the run-creation path and trace how resource requests are compared with the available node pools. Confirm how an unsatisfiable request currently becomes pending, then identify the existing run-creation tests or validation entry point. Done means an impossible request returns an error instead of remaining pending indefinitely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100