-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
Send promise resolution messages #471
Conversation
Needs testing.
Added a (failing) test. Stay tuned. |
Leaks a client; need to investigate.
Test is fixed. |
Tacked on another commit to handle a remote peer that doesn't understand resolve messages; without this, we'd leak caps. |
...which hangs. Some debugging suggests that this *is* being removed from the table, but I need to figure out why the cap isn't actually released.
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. Note the failing CI though.
Yeah, I need to figure out why that test is failing -- I did some debugging, and the export is definitely being popped from the table, so I'm not sure why Shutdown() isn't actually being called. I'll keep you posted. |
At some point in the past, Resolver was called Fulfiller; this is left over from that.
Alright, last commit fixes the test. |
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.
This patch updates sendCap such that it checks whether it should send senderHosted or senderPromise for an export. If the latter, it also arranges for a Resolve message to be sent when the promise is resolved.
Still TODO:
Note: this patch adds a helper method to marshal an
error
into anException
.