fix: Replace Date.now() with performance.now()#298
Open
CptLemming wants to merge 1 commit intorsocket:1.0.x-alphafrom
Open
fix: Replace Date.now() with performance.now()#298CptLemming wants to merge 1 commit intorsocket:1.0.x-alphafrom
CptLemming wants to merge 1 commit intorsocket:1.0.x-alphafrom
Conversation
performance.now() uses a monotonic clock, preventing clock skew
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.
When using WebsocketClientTransport I've noticed if a users local clock gets adjusted, a connection timeout is triggered:
This is caused by keeping track of timeout with
Date.now()which doesn't account for clock skew.See https://developer.mozilla.org/en-US/docs/Web/API/Performance/now#performance.now_vs._date.now