oxidecomputer / oxidecomputer/rfd-api
Support rerunning jobs
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 95
- Forks
- 22
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 17
Description
Currently we have a unique index on the rfd number, commit pair. This prevents us from re-executing a job. Additionally we do not have a mechanism for updating an existing revision.
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 locating the unique index on the RFD number and commit pair, then trace the job and revision handling that currently rejects duplicate executions. Done means a job can be rerun and an existing revision can be updated without violating the data model.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100