- Notifications
You must be signed in to change notification settings - Fork1k
chore: add explicit Wait() to clock.Advance()#13464
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
spikecurtis commentedJun 4, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
This stack of pull requests is managed by Graphite.Learn more about stacking. Join@spikecurtis and the rest of your teammates on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
LGTM 👍 I'm assuming the linter complaints are due to stacking.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
e243711
to63c9374
Compare1f3c4aa
tob55fc1a
Compareb55fc1a
to35daa55
Compare35daa55
to6e5decd
CompareMerge activity
|
Uh oh!
There was an error while loading.Please reload this page.
Modifies
clock.Mock.Advance()
to allow explicitly waiting for advance to complete. E.g.Having the wait be explicit allows you to more easily write tests where the timer or ticker calls back into the
clock
with something you have a trap set for, e.g.