fix: pass Unix seconds (not milliseconds) to commit timestamp#76
Open
sindrest wants to merge 1 commit into
Open
fix: pass Unix seconds (not milliseconds) to commit timestamp#76sindrest wants to merge 1 commit into
sindrest wants to merge 1 commit into
Conversation
Loro expects Unix seconds, but Date.now() returns milliseconds.
On loro-crdt@1.10.2 () the explicit timestamp is
ignored, but on >=1.10.6 it's respected. This is causing sync-plugin
commit millisecond timestamps, which leads to errors downstream
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Loro expects Unix seconds, but Date.now() returns milliseconds.
On loro-crdt@1.10.2 (the current locked version) the explicit timestamp is ignored, but on >=1.10.6 it's respected. This is causing sync-plugin commit millisecond timestamps, which leads to errors downstream