feat: use orchFns.autoStake as target for receiveUpcall
#10065
Conversation
Deploying agoric-sdk with
|
| Latest commit: |
937c55b
|
| Status: | 🚫 Build failed. |
| trace('receiveUpcall', event); | ||
| const { localAccount, stakingAccount, config } = this.state; | ||
| // eslint-disable-next-line no-use-before-define -- defined by orchestrateAll, necessarily after this | ||
| orchFns.autoStake(localAccount, stakingAccount, config, event); |
There was a problem hiding this comment.
I wanted to do orchFns.autoStake(this.state, event) here, and call it ~(continuingOfferCtx, event) on the other end, but was greeted with Error: cannot serialize Remotables with accessors like "localAccount"
There was a problem hiding this comment.
you might try passing a copy with normal properties rather than accessors {... this.state }.
There was a problem hiding this comment.
This was my observation with this approach unfortunately: #10991 (comment)
There was a problem hiding this comment.
odd. I'm almost certain that I've done it.
| * stakingAccount: GuestInterface<CosmosOrchestrationAccount>; | ||
| * localAccount: GuestInterface<LocalOrchestrationAccount>; |
There was a problem hiding this comment.
If we use OrchestrationAccount<any>, which the flow is expecting, we see Argument of type '<OrchestrationAccount<any>>' is not assignable to parameter of type 'Passable'. on L105.
- uses an async-flow function as the handler for a `.monitorTransfers()` tap - allows guest develoeprs to write handlers as flows instead of with vows and watchers
0xpatrickdev
force-pushed
the
10047-monitor-transfers-flow
branch
from
5b8b568 to
5f50d92
Compare
closes: #10047
Description
Rework
auto-stake-it.contract.jsto use an orchestrated async-flow as the handler for.monitorTransfers()(vtransfer). Previously, it was written using vows and watchers.Security Considerations
n/a
Scaling Considerations
n/a
Documentation Considerations
Better example code for prospective developers.
Testing Considerations
Covered by existing contract test and e2e test in
multichain-testingUpgrade Considerations
n/a, example code