hq issue 217's remaining half. The TypeScript runtime's raw subscription that answers discovery ran its loop unguarded; a refusal escaped as an unhandled rejection and ended the process — which is what crash-looped every per-module container on 2026-10-03 over a subscription that only serves discovery. Now caught, logged ("discovery will not see this runtime there, and it serves on"), and the runtime keeps serving. New test against a NATS server whose permissions deny $SRV.PING.> (fixture config; MESH_TEST_REFUSING_NATS): passes, and fails without the fix. Full TS suite 38/38. (The Go runtime already logs a refused announcement and carries on.)
hq issue 217's remaining half. The TypeScript runtime's raw subscription that answers discovery ran its loop unguarded; a refusal escaped as an unhandled rejection and ended the process — which is what crash-looped every per-module container on 2026-10-03 over a subscription that only serves discovery. Now caught, logged ("discovery will not see this runtime there, and it serves on"), and the runtime keeps serving. New test against a NATS server whose permissions deny `$SRV.PING.>` (fixture config; `MESH_TEST_REFUSING_NATS`): passes, and fails without the fix. Full TS suite 38/38. (The Go runtime already logs a refused announcement and carries on.)
The raw subscription that answers discovery ran its loop unguarded, so a refusal escaped as an
unhandled rejection and ended the process: every per-module container crash-looped on 2026-10-03
over a subscription that only serves the mesh seeing the runtime. It is now caught, logged, and the
runtime serves on. Tested against a bus whose permissions refuse the subject; fails without it.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
hq issue 217's remaining half. The TypeScript runtime's raw subscription that answers discovery ran its loop unguarded; a refusal escaped as an unhandled rejection and ended the process — which is what crash-looped every per-module container on 2026-10-03 over a subscription that only serves discovery. Now caught, logged ("discovery will not see this runtime there, and it serves on"), and the runtime keeps serving. New test against a NATS server whose permissions deny
$SRV.PING.>(fixture config;MESH_TEST_REFUSING_NATS): passes, and fails without the fix. Full TS suite 38/38. (The Go runtime already logs a refused announcement and carries on.)