chain-client-sdk-ts/test
flemming-it 2131193f1f fix: come back quickly after a hub restart, and pin the dependencies
Two things helloeco ran into while wiring the gateway.

grpc-js waits a second before its second reconnect attempt and backs
off towards two minutes. That is right for a far-away service and
wrong for a hub on the same network: after a restart or a deploy a
gateway sits out the backoff with requests in hand. The client now
sets initial 200 ms and a 5 s ceiling, and a caller's own
channelOptions still win. The client exposes the options it ended up
with, which is the only way to tell a default that applies from one
that was silently replaced.

The dependencies are pinned exactly instead of by range. This package
is consumed by a handful of services, not by a library ecosystem, and
a surprise minor of grpc-js is what breaks a portal at three in the
morning. Raising one is a commit, with the skew job in front of it.

Guards: the defaults and the precedence are asserted (probed by
mutation), plus a case that a run works again once the hub is back.

Signed-off-by: flemming-it <sf@flemming.it>
2026-10-27 03:01:08 +01:00
..
client_against_fake.test.ts fix: come back quickly after a hub restart, and pin the dependencies 2026-10-27 03:01:08 +01:00
errors.test.ts feat: TypeScript client for Node, with a scriptable fake hub 2026-10-27 00:59:57 +01:00
payload.test.ts feat: TypeScript client for Node, with a scriptable fake hub 2026-10-27 00:59:57 +01:00
proto_copy.test.ts feat: TypeScript client for Node, with a scriptable fake hub 2026-10-27 00:59:57 +01:00
real_hub.test.ts feat: idempotency key, the INTERRUPTED phase, and a real-hub skew suite 2026-10-27 01:32:58 +01:00