-
Notifications
You must be signed in to change notification settings - Fork 229
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
Allow vats under SwingSet to unwrap their promises #674
Conversation
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.
Sounds ok to me. I'll defer to @erights about whether unwrap
is ocap-safe, but I don't think I've heard him object.
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.
This looks good. I think there was some previous discussion about reusing the package @agoric/make-promise. Was there a reason not to do that? I can't remember
Oh! I didn't remember about |
yep, just opened an issue |
The same fix was recently implemented in https://github.com/Agoric/agoric-sdk/pull/623/files#diff-f63ab4d221058b2338f0582969e18090
+1 |
Huh, ok github's "open related issue" didn't do what I expected. Landing this (#674) PR will not resolve the new (#682) bug.. we need to change SwingSet to depend on make-promise (and use it internally, in lieu of it's own copy) to resolve #682. Did github edit the top comment of this PR when I used the "open related issue" button? I think we should edit the top comment to remove the claim that it closes the new ticket. |
Yep, was in the midst of pushing new state and updated the issue in the wrong order. |
Use @agoric/make-promise to make Promises that can be unwrapped (currently via the HandledPromise shim, but that may change).
439927e
to
f2be5c7
Compare
I edited the comment to remove the magic bug-closing words |
I put back the bug-closing words since that's now what this PR does. 😉 I should not have updated it preemptively. Too many balls in the air. |
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.
looks good, and yeah that closes the other ticket now
Refs #74
Closes #682
Use
@agoric/make-promise
instead of the builtinmakePromise.js
that doesn't properly unwrap.