pyronear / pyronear/pyro-annotator
Sequence delete leaks S3 objects (rollback path of the object-split importer)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 2
Description
The object-split importer (#166/#176, hardened in #177) rolls back partially-imported object sequences by deleting the sequence via the API. The delete cascades DB rows only — detection images already bucket-copied (or /from-url fetched) into the annotation S3 bucket are left behind as orphaned objects.
Since rollback is now a routine automatic path (partial detection failure, annotation-write failure), flaky runs accumulate orphans. Either delete the sequence's S3 objects in the delete endpoint, or add a periodic orphan sweep — or explicitly document the leak as accepted.
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 with the object-split importer and the sequence delete endpoint described in the issue, then trace the rollback path and how bucket-copied or /from-url objects are tracked. Done requires an agreed policy—cleanup during deletion, a periodic orphan sweep, or explicit documentation—and coverage for the chosen behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100