When deleting an org, the validator client is not deleted.
Open
Nobody has claimed this yet.
Aspect: Performance
Status: To be prioritized
Triage: Confirmed
Type: Bug
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
This can be corrected by either explicitly deleting the client in the code, or implementing a CASCADE DELETE foreign key from clients -> orgs.
If we implement the latter, we will still orphan the client's authz entries.
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
No files, tests, or entry points are named. Start by tracing organization deletion and the persistence paths for clients and authorization entries, then determine the intended cleanup behavior and verify that deletion does not leave orphaned records.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100