-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[ReadHandler] Unify Now timestamps #27920
Comments
The reason this matters: we can get radically different (hundreds of milliseconds apart) values for two consecutive now() calls on Mac/Linux, and the code very much does not expect that to happen as it's written now. |
@lpbeliveau-silabs For future reference, links to comments in the "files" view go dead when the code changes... You probably want:
to link to the comments in the main discussion view... (note that the comment ids are the same). |
Solved by #28657 |
In the report Scheduler, we are calling get monotonic timestamp several times in a row to establish a "now" moment. Rework needed so the same timestamp is used instead of consecutive calls to get monotonic timestamp.
The text was updated successfully, but these errors were encountered: