oxidecomputer / oxidecomputer/crucible
a follow-up issue to track the question of retries in general.
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
This is a tracking issue to come back and look at the retries in the scrubber.
Originally posted by @jmpesp in https://github.com/oxidecomputer/crucible/pull/432#pullrequestreview-1115541336
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 locating the scrubber implementation and reviewing the linked pull request #432, especially the discussion that prompted this tracking issue. The issue does not define the retry behavior, affected files, tests, or completion criteria, so those requirements need to be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100