Handle cameras deletion cascade for poses, sequences, detections, and storage cleanup
Open
Nobody has claimed this yet.
endpoint: cameras
- Dominant language
- Python
- Stars
- 29
- Forks
- 14
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 5
Description
Pitch
Same consideration as #541 Handle organization deletion cascade for cameras, sequences, detections, and storage cleanup
Moreover, camera deletion endpoint return a 500 !
Needs cascade deletion, and would be relevant to handle this issue as FG suggested it in 541
- for postgres cascade deletion we use native postgres features (cf. cascade delete)
- once that's done, we can handle blob deletion (bucket objects)
Thanks a lot 🙏
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 reading issue #541 and locating the camera deletion endpoint in the FastAPI application. Check the PostgreSQL cascade-delete guidance referenced here, then determine how bucket objects are removed; done means camera deletion no longer returns 500, related poses, sequences, and detections are deleted, and associated storage objects are cleaned up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, postgresql, python
- Domain
- api, backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100