test(boot): simulate incoming vtransfer bridge events

[0xpatrickdev]

closes: #10131

Description

• adds runInbound to bridgeUtils in bootstrap test support to simulate an incoming bridge events, like a packet acknowledgement
• updates send-anywhere boot test so it's no longer failing
  • leaves contract upgrade aspect of test TODO until upgrade tests of Orch contracts restarting during a flow #9303

Security Considerations

n/a

Scaling Considerations

n/a

Documentation Considerations

n/a

Testing Considerations

Addreses a test.failing checked in

Upgrade Considerations

n/a, example contract and test support tools

[cloudflare-workers-and-pages]

Deploying agoric-sdk with    Cloudflare Pages

Latest commit:	7508618
Status:	✅  Deploy successful!
Preview URL:	https://baf1cebc.agoric-sdk.pages.dev
Branch Preview URL:	https://10131-vtransfer-boot.agoric-sdk.pages.dev

View logs

[turadg]

why remove these assurances?

[0xpatrickdev]

We are not sending or recieving any DIBC bridge messages in send-anywhere, so flushing the queue (which only has DIBC messages) seemed unnecessary

[turadg]

this strikes me as too high level for bridgeUtils. The name also doesn't convey how it's different from simply inbound(BridgeId.VTRANSFER, buildVTransferEvent(params)),

WDYT of,

Suggested change

	async inboundVTransferEvent(params: BuildVTransferEventParams) {
	await runUtils.queueAndRun(
	() => inbound(BridgeId.VTRANSFER, buildVTransferEvent(params)),
	true,
	);
	},
	async runInbound(...args: Parameters<typeof inbound>>) {
	await runUtils.queueAndRun(
	() => inbound(...args),
	true,
	);
	},

If we want better autocomplete we could improve the underlying inbound type to look at the first arg to narrow the rest.

[0xpatrickdev]

Sure, Parameters<typeof inbound> is just ...any[], so I narrowed to ask for BridgeId for the first argument.

[turadg]

I think this is too abstract for BridgeUtils. (see comment below)

Putting a suggestion here to see how it looks:

Suggested change

	await inboundVTransferEvent({
	sourceChannel: 'channel-5',
	sequence: '1',
	});
	await runInbound(BridgeId.VTRANSFER, buildVTransferEvent({
	sourceChannel: 'channel-5',
	sequence: '1',
	});

(and drop the export for BuildVTransferEventParams)

If that's too clunky, ibc-mocks.ts could have a helper like,

const makeRunIbcTransfer = (queueInbound) => 
  (event: Parameters<typeof buildVTransferEvent>[0]) => queueInbound(BridgeId.VTRANSFER, buildVTransferEvent(event);

and this could be,

Suggested change

	await inboundVTransferEvent({
	sourceChannel: 'channel-5',
	sequence: '1',
	});
	await runIbcTransfer({
	sourceChannel: 'channel-5',
	sequence: '1',
	});