A refused announcement is said, never fatal (hq issue 217)

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.
2026-10-03 23:24:38 +02:00
parent bc05658772
commit 6ba0f4dc1e
3 changed files with 59 additions and 3 deletions
@@ -0,0 +1,10 @@
+# A bus that refuses one subject: what the mesh's grants do to a subject they do not name (issue 217).
+authorization {
+  users = [
+    { user: "runtime", password: "runtime", permissions: {
+        publish: { allow: [">"] }
+        subscribe: { allow: [">"], deny: ["$SRV.PING.>"] }
+    } }
+  ]
+}
+jetstream: enabled