-
Notifications
You must be signed in to change notification settings - Fork 212
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
6000 reduce floating promises #9416
Conversation
Deploying agoric-sdk with Cloudflare Pages
|
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.
One correction. The rest looks good.
@@ -78,7 +77,7 @@ test('tick does not flush by default', async t => { | |||
const handler = Far('handler', { | |||
wake: scheduled => { | |||
woken = scheduled; | |||
stallLots().then(() => (later = true)); | |||
void stallLots().then(() => (later = true)); |
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.
I think these should be await
. stallLots()
is just a delay. it does nothing with void
.
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.
Since I punted some Zoe already I just punted the rest of Zoe to https://github.com/Agoric/agoric-sdk/compare/6000-no-zoe-floating-promises
(I lost one of my commits, unfortunately, but that has the Zoe one from this branch.)
8c54d65
to
98614ce
Compare
98614ce
to
e332a3a
Compare
refs: #6000
Description
I keep seeing these warnings and they're distracting. This burns down almost all of them. What's left are a handful in Zoe that may be best for @Chris-Hibbert to tackle directly.
Security Considerations
none
Scaling Considerations
none
Documentation Considerations
none
Testing Considerations
Some of these change the test. Reviewers should be confident in the changes.
Upgrade Considerations
None of these should change the end-user API. Some may fix bugs.