You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been working on making the network and IBC vats durable (#8721). Leftover work from this initiative is that we haven't made promises durable yet, which prevents us from truly being able to upgrade.
Description of the Design
As part of the vow(whenable) work, we've created promise watchers that are durable and can ensure that a promise is reconnected on upgrade. We need to go through the two vats and migrate any code awaiting on a Vow to use a watcher insead
open design questions:
use the vow-capable E work-alike?
convert all awaits? or are there short-lived ones that should not be converted?
Security Considerations
Scaling Considerations
Test Plan
upgrade / restart the vats at many points in the state machine
Upgrade Considerations
The content you are editing has changed. Please copy your edits and refresh the page.
Following the upgrade-at-each-point-in-a-flow test pattern, I'm trying to do some testing work to establish where the finish line is. I don't yet have a test failing in a way that shows that we're not already there. :-/
What is the Problem Being Solved?
We've been working on making the network and IBC vats durable (#8721). Leftover work from this initiative is that we haven't made promises durable yet, which prevents us from truly being able to upgrade.
Description of the Design
As part of the
vow
(whenable) work, we've created promise watchers that are durable and can ensure that a promise is reconnected on upgrade. We need to go through the two vats and migrate any code awaiting on a Vow to use a watcher inseadopen design questions:
E
work-alike?Security Considerations
Scaling Considerations
Test Plan
Upgrade Considerations
Tasks
Remote<T>
to indicate tolerance of far types #9027The text was updated successfully, but these errors were encountered: