Replace time.time with time.monotonic to avoid clock drift issues#4492
Merged
Torxed merged 1 commit intoarchlinux:masterfrom Apr 28, 2026
Merged
Replace time.time with time.monotonic to avoid clock drift issues#4492Torxed merged 1 commit intoarchlinux:masterfrom
Torxed merged 1 commit intoarchlinux:masterfrom
Conversation
Using time.time() can be inaccurate if the system clock gets updated in between calls.
Torxed
approved these changes
Apr 28, 2026
Member
Torxed
left a comment
Torxed
left a comment
There was a problem hiding this comment.
This one really tickles my mind for some reason, nice improvement!
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
2 participants
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.
PR Description:
Using time.time() can be inaccurate if the system clock gets updated in between calls.
Tests and Checks