Race condition when saving/syncing
Open
Nobody has claimed this yet.
1. to develop
bug
feature: sync
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
I have a report with a har file dump for a shortly popping up conflict dialog that seems to be caused by a race between the save and sync request where both are issued roughly at the same time but the save happens and therefore the sync returns a temporary conflict
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 with the reported HAR dump and compare the save and sync requests, which are described as occurring at roughly the same time. Reproduce the conflict dialog and trace the request ordering; done means simultaneous saving and syncing no longer produces a temporary conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100