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>
This commit is contained in:
flemming-it 2026-10-27 03:00:55 +01:00
parent 986377f1df
commit 2131193f1f
4 changed files with 86 additions and 6 deletions

View file

@ -32,11 +32,11 @@
"check": "tsc -p tsconfig.json --noEmit && tsc -p tsconfig.test.json --noEmit"
},
"dependencies": {
"@grpc/grpc-js": "^1.14.0",
"@grpc/proto-loader": "^0.8.0"
"@grpc/grpc-js": "1.14.6",
"@grpc/proto-loader": "0.8.1"
},
"devDependencies": {
"@types/node": "^22.10.0",
"typescript": "^5.9.0"
"@types/node": "22.20.5",
"typescript": "5.9.3"
}
}