oxidecomputer / oxidecomputer/omicron
inspect TUF repo generation transaction logic more closely
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
https://github.com/oxidecomputer/omicron/pull/7519 modifies the transaction that adds TUF repo metadata to the database, adding a generation number that is used to assist in replicating artifacts. I'm not sure if this transaction will be retried in all cases.
Discussion: https://github.com/oxidecomputer/omicron/pull/7519#discussion_r1983927745
Contributor guide
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 reviewing PR #7519 and the linked discussion, then trace the transaction that adds TUF repository metadata to the database. Determine whether transaction retries cover every relevant failure case and document the concrete gap or confirm that retry behavior is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100