-
Notifications
You must be signed in to change notification settings - Fork 214
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
chore(fusdc): settle ForwardFailed
and Advancing
txs
#10729
base: master
Are you sure you want to change the base?
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.
a couple notes before our chat
} catch (e) { | ||
// settlement already received; tx will Forward. |
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.
assuming all exceptions have this meaning seems inconsistent with https://github.com/Agoric/agoric-sdk/wiki/Errors-and-Control-Flow
if (mintedEarly.has(key)) { | ||
mintedEarly.delete(key); | ||
void this.facets.self.forward(txHash, fullValue, destination.value); | ||
throw Fail`${q(txHash)} minted before Observed`; |
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 should be "raising a non-error" per house style on Errors and Control Flow
d044624
to
28e969b
Compare
- tx to Forward will always have `txHash` - `Advancing` txs can be dequeued and added to `mintedEarly` - handle "minted before Observed" by adding to `mintedEarly` store - `Advancer` checks if tx is in `mintedEarly` store
- use `notifyFacet` is used to simulate Advance - test that "minted early" forwards if evidence eventually reported - test `ForwardFailed` state (slow `.forward` transfer fails) - test "minted while `Advancing`" scenarios (`Advanced`, `AdvanceFailed`)
28e969b
to
f5df91a
Compare
closes: #10625
Description
Security Considerations
Scaling Considerations
Documentation Considerations
Testing Considerations
Upgrade Considerations