-
Notifications
You must be signed in to change notification settings - Fork 3
π¨ CRITICAL: Fix data loss bug when lastSyncAt is null #42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new branch always compares vector clocks when
lastSyncAtis null, but the result is only used to guard on the'concurrent'case before continuing. WhencompareVectorClocksreturns'b_before_a'(local clock ahead of remote), the code still falls through to "apply change" and writes the remote payload over the newer local record, merely merging clocks afterwards. This still causes data loss in the exact reinstall/reset scenario being fixed: if a user has unsynced local edits and the server returns an older version, those edits are overwritten instead of being preserved or pushed upstream. The conflict detection should also skip applying remote data (or push local changes) whenever the local clock dominates the remote clock, not just when clocks are concurrent.Useful? React with πΒ / π.