ERR_SUBMIT_TRANSFORM_OPS_NOT_FOUND recovery
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.5k
- Forks
- 456
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 5
Description
Hi,
we are deleting old ops from our oplog to make sure it does not grow without bounds. As a result, we sometimes encounter ERR_SUBMIT_TRANSFORM_OPS_NOT_FOUND if a client reconnects after a long time without connection. I am wondering what would be the best way to recover on client side.
I believe we could just manually call _hardRollback if we hit the error when submitting ops. Is there are reason sharedb itself does not do it already?
Thanks!
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 locating the handling for ERR_SUBMIT_TRANSFORM_OPS_NOT_FOUND and the client-side _hardRollback method. Determine whether submitting operations after deleted oplog entries should trigger recovery automatically, and define the expected behavior before adding or updating coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100