Simultaneous puts to a path (tree vs. non-tree) results in incorrect tree
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
Doing a tree put while simultaneously put-ing something else to the same total tree path results in an object with _id keys in it rather than either the object or the link. The object cannot be deleted because the graph is invalid and causes permissions handler to say that the user who made it does not have permission to it.
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
No files, tests, or entry points are named. Start by reproducing simultaneous puts to the same tree path against the OADA server, then trace the tree-versus-link handling and permissions failure. Done means concurrent puts leave a valid object or link that can be deleted and does not trigger an incorrect permission error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100