oxidecomputer / oxidecomputer/falcon
destroy does not always destroy backing images
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 20
- Forks
- 5
- Avg merge
- 11d 13h
- Merged PRs (30d)
- 2
Description
Sometimes it takes multiple attempts to destroy images, and there is no indication that the first attempt failed.
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 reproducing the destroy operation and tracing how backing images are handled across repeated attempts. Confirm the failure condition and ensure a destroy attempt consistently removes the backing images or clearly reports when it does not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100