-
Notifications
You must be signed in to change notification settings - Fork 208
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
9449 chain facades return vows #9547
Conversation
Deploying agoric-sdk with Cloudflare Pages
|
// FIXME use watch() from vowTools | ||
return watch(allVows([icaP, V(icaP).getAddress()]), { |
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.
Why not destructure from L42 and wrap the watcher in a Far
?
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.
Because I want it to be more likely to fail in testing.
In const vowTools = prepareVowTools(zone.subZone('vows')); Do we not pass them around to the relevant places? |
They're available. See https://github.com/Agoric/agoric-sdk/pull/9547/files#r1648321242 |
@Mergifyio requeue |
✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically |
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 to me like some tiny changes would make the vows durable
orchestration, | ||
storageNode, | ||
timer, | ||
vowTools: { allVows }, |
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.
If we get watch
from these vowTools
, it'll make durable vows, right?
@@ -1,13 +1,14 @@ | |||
/** @file ChainAccount exo */ | |||
import { makeTracer } from '@agoric/internal'; | |||
import { V } from '@agoric/vow/vat.js'; | |||
import { V, watch } from '@agoric/vow/vat.js'; |
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.
How about getting watch
from the durable vowTools
? See below.
omni.makeAccount(), | ||
agoric.makeAccount(), | ||
// XXX when() until membrane | ||
when(omni.makeAccount()), |
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.
The vowTools
from the call to provideOrchestration
are durable, right? How about getting when
from there?
@@ -4,6 +4,7 @@ import { withdrawFromSeat } from '@agoric/zoe/src/contractSupport/zoeHelpers.js' | |||
import { Far } from '@endo/far'; | |||
import { deeplyFulfilled } from '@endo/marshal'; | |||
import { M, objectMap } from '@endo/patterns'; | |||
import { when } from '@agoric/vow/vat.js'; |
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.
see below re durable vowTools...
@@ -1,5 +1,5 @@ | |||
/** @file ChainAccount exo */ | |||
import { V } from '@agoric/vow/vat.js'; | |||
import { V, watch } from '@agoric/vow/vat.js'; |
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.
again, a durable version is reasonably handy...
makeLocalOrchestrationAccountKit, | ||
localchain, | ||
storageNode, | ||
vowTools: { allVows }, |
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.
a durable watch
is available in these vowTools
, right?
a260b71
to
f9b6857
Compare
refs: #9449
Description
More exos returning vows. Note these are heap vows due to
agoric-sdk/packages/vow/vat.js
Lines 29 to 31 in 944adea
Security Considerations
none
Scaling Considerations
none
Documentation Considerations
none
Testing Considerations
CI
Upgrade Considerations
none