fix(clock): make sure runTo is atomic #37699
Open
+147
−34
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.
Since
runTo
is asynchronous, we might end up in a reentrant call, for example whenupdateRealTimeTimer
timeout happens between two tasks inrunTo
. This yields to breaking all invariants and results innow
being reset to some old value.To prevent this, introduce a semaphore and only allow a single
runTo
at a time.Additionally, update real time timer after
runTo
, otherwise it might be scheduled for some time in the past when fast-forwarding.Drive-by:
debugDump()
for debuggingFixes #37635.