Registers the fix of hq issue 353 (pull request on hq to follow). Do not merge without review.
Measured on the control node, 2026-10-09 (local times, the controller's journal, process 657383):
17:32 the router (messenger) was unassigned so the catalogue's merge gate had nothing to send; 17:52:54 a walk (sudo) pushed the control node, composing the bus's user list without the controller's grant to ask: asksSeatOf composes it from a holder of operator-channel that is assigned, and none was.
17:54:05 the asker started (the router was assigned again by then, so routerHere said yes) and the bus refused mesh.seat.operator-channel.accept.ask.mesh-controller on connection [510888]: seven refusals until 17:56:05, each followed by "the operator could not be asked about machine.shanks.units: context deadline exceeded".
17:55:56 the rollout push sent the control node the user list with the grant ("sent novox 504 resource(s)"); 17:56:05 the bus reloaded it in place (the same second the watchdogs saw "jetstream not enabled", the reload's blip); 17:56:10 the same connection asked successfully ("asked the operator about machine.shanks.units (cbefe756485f6d8ba): 1 answer(s)"), and 18:03:53 again. No reconnect: the server applies a reloaded permission to a standing connection.
The condition bus.controller.refused stays open for an hour after the last refusal (S9's advisoryQuiet) and clears by itself at about 18:56.
Cause. The controller's grant to ask is composed from the router's assignment and reaches the bus only when the bus's machine is next pushed. Between assign and push — and on any push of that machine made while the router is unassigned — the record says a router is here and the bus refuses every ask. The composition is right (the grant follows the holder, as ADR 0259 §3 says); the asker trusted the record before the bus held it.
Fix. The asker judges, as a push does (brokerBehind), whether the machine holding the bus was last sent the user list composed now. While it was not: nothing is published, it is said once, and the conditions that need the operator are raised as asks-undelivered naming what carries the grant ("push novox carries it"). Judged at most every 30 s, because composing the list resolves the bus's machine whole.
Tests.TestNothingIsAskedWhileTheBusLacksTheControllersGrant: nothing asked while the bus lacks the grant, said once, raised as undelivered with the push named, asked once the bus holds it, the condition cleared. Before the fix the asker has no such gate, so the test does not compile against it (the field it drives is the fix).
sh merge-check.sh runs locally against a throwaway store; its verdict and the forge's are read before merging (issue 341: the branch is on main's head, so the head is the merge result).
Registers the fix of hq issue 353 (pull request on hq to follow). Do not merge without review.
**Measured on the control node, 2026-10-09 (local times, the controller's journal, process 657383):**
- 17:32 the router (messenger) was unassigned so the catalogue's merge gate had nothing to send; 17:52:54 a walk (sudo) pushed the control node, composing the bus's user list **without** the controller's grant to ask: `asksSeatOf` composes it from a holder of `operator-channel` that is *assigned*, and none was.
- 17:54:05 the asker started (the router was assigned again by then, so `routerHere` said yes) and the bus refused `mesh.seat.operator-channel.accept.ask.mesh-controller` on connection [510888]: seven refusals until 17:56:05, each followed by "the operator could not be asked about machine.shanks.units: context deadline exceeded".
- 17:55:56 the rollout push sent the control node the user list **with** the grant ("sent novox 504 resource(s)"); 17:56:05 the bus reloaded it in place (the same second the watchdogs saw "jetstream not enabled", the reload's blip); 17:56:10 the same connection asked successfully ("asked the operator about machine.shanks.units (cbefe756485f6d8ba): 1 answer(s)"), and 18:03:53 again. No reconnect: the server applies a reloaded permission to a standing connection.
- The condition `bus.controller.refused` stays open for an hour after the last refusal (S9's `advisoryQuiet`) and clears by itself at about 18:56.
**Cause.** The controller's grant to ask is composed from the router's assignment and reaches the bus only when the bus's machine is next pushed. Between `assign` and `push` — and on any push of that machine made while the router is unassigned — the record says a router is here and the bus refuses every ask. The composition is right (the grant follows the holder, as ADR 0259 §3 says); the asker trusted the record before the bus held it.
**Fix.** The asker judges, as a push does (`brokerBehind`), whether the machine holding the bus was last sent the user list composed now. While it was not: nothing is published, it is said once, and the conditions that need the operator are raised as `asks-undelivered` naming what carries the grant ("`push novox` carries it"). Judged at most every 30 s, because composing the list resolves the bus's machine whole.
**Tests.** `TestNothingIsAskedWhileTheBusLacksTheControllersGrant`: nothing asked while the bus lacks the grant, said once, raised as undelivered with the push named, asked once the bus holds it, the condition cleared. Before the fix the asker has no such gate, so the test does not compile against it (the field it drives is the fix).
`sh merge-check.sh` runs locally against a throwaway store; its verdict and the forge's are read before merging (issue 341: the branch is on main's head, so the head is the merge result).
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Machines
mesh-controller on novox: passed — healthy 3 times over 3m59s
mesh-controller on the rest running it: sent
build-agent on ace: passed — healthy 3 times over 3m25s
build-agent on the rest running it: sent
route-proxy on ace: passed — healthy 3 times over 3m39s
route-proxy on the rest running it: sent
Transitions
2026-10-09 16:18 (new) → proposed (announced): novox/mesh-controller#186's head announced
2026-10-09 16:24 proposed → checked (checked): the verdict names this commit
2026-10-09 16:24 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 17:34 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-09 17:34 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
2026-10-09 17:49 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-controller@0c8c9ffae990` — **delivered** since 2026-10-09T17:49:53Z
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 3m59s
- mesh-controller on the rest running it: sent
- build-agent on ace: passed — healthy 3 times over 3m25s
- build-agent on the rest running it: sent
- route-proxy on ace: passed — healthy 3 times over 3m39s
- route-proxy on the rest running it: sent
**Transitions**
- 2026-10-09 16:18 (new) → proposed (announced): novox/mesh-controller#186's head announced
- 2026-10-09 16:24 proposed → checked (checked): the verdict names this commit
- 2026-10-09 16:24 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 17:34 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-09 17:34 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
- 2026-10-09 17:49 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
The grant is composed from the router's assignment and reaches the bus when its machine is next
pushed. Between assign and push the record said a router was here and the bus refused every ask
(seven refusals on 2026-10-09, 17:54 to 17:56). The asker now judges, as a push does, whether the
bus's machine was last sent the user list composed now; while it was not, nothing is published, it
is said once, and the conditions that need the operator are raised as undelivered, naming the push
that carries the grant.
jschoubben
force-pushed fix/353-the-controller-asks-only-once-the-bus-holds-its-grant from 42e7592ddf to 0c8c9ffae92026-10-09 16:18:48 +00:00Compare
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on shanks as build-1791562733804018506 (builds --log build-1791562733804018506).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 54 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T16:12:14Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T16:12:14Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.040s
ok github.com/novox/mesh-controller/cmd/mesh-controller 219.167s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.036s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.042s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.032s
ok github.com/novox/mesh-controller/examples/route-proxy 1.227s
ok github.com/novox/mesh-controller/internal/artifacts 1.073s
ok github.com/novox/mesh-controller/internal/broker 2.767s
ok github.com/novox/mesh-controller/internal/builder 1.943s
ok github.com/novox/mesh-controller/internal/catalogue 5.007s
ok github.com/novox/mesh-controller/internal/conditions 2.558s
ok github.com/novox/mesh-controller/internal/envfile 1.046s
ok github.com/novox/mesh-controller/internal/facts 1.055s
ok github.com/novox/mesh-controller/internal/identity 4.752s
ok github.com/novox/mesh-controller/internal/inventory 87.314s
ok github.com/novox/mesh-controller/internal/lease 17.700s
ok github.com/novox/mesh-controller/internal/licences 4.323s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.033s
ok github.com/novox/mesh-controller/internal/link 53.472s
ok github.com/novox/mesh-controller/internal/lint 2.230s
ok github.com/novox/mesh-controller/internal/outward 1.074s
ok github.com/novox/mesh-controller/internal/overlay 1.062s
ok github.com/novox/mesh-controller/internal/secrets 1.525s
ok github.com/novox/mesh-controller/internal/store 3.445s
ok github.com/novox/mesh-controller/internal/testbus 1.228s
ok github.com/novox/mesh-controller/internal/token 1.014s
**Merge check** at `0c8c9ffa`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on shanks as `build-1791562733804018506` (`builds --log build-1791562733804018506`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 54 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T16:12:14Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T16:12:14Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.040s
ok github.com/novox/mesh-controller/cmd/mesh-controller 219.167s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.036s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.042s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.032s
ok github.com/novox/mesh-controller/examples/route-proxy 1.227s
ok github.com/novox/mesh-controller/internal/artifacts 1.073s
ok github.com/novox/mesh-controller/internal/broker 2.767s
ok github.com/novox/mesh-controller/internal/builder 1.943s
ok github.com/novox/mesh-controller/internal/catalogue 5.007s
ok github.com/novox/mesh-controller/internal/conditions 2.558s
ok github.com/novox/mesh-controller/internal/envfile 1.046s
ok github.com/novox/mesh-controller/internal/facts 1.055s
ok github.com/novox/mesh-controller/internal/identity 4.752s
ok github.com/novox/mesh-controller/internal/inventory 87.314s
ok github.com/novox/mesh-controller/internal/lease 17.700s
ok github.com/novox/mesh-controller/internal/licences 4.323s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.033s
ok github.com/novox/mesh-controller/internal/link 53.472s
ok github.com/novox/mesh-controller/internal/lint 2.230s
ok github.com/novox/mesh-controller/internal/outward 1.074s
ok github.com/novox/mesh-controller/internal/overlay 1.062s
ok github.com/novox/mesh-controller/internal/secrets 1.525s
ok github.com/novox/mesh-controller/internal/store 3.445s
ok github.com/novox/mesh-controller/internal/testbus 1.228s
ok github.com/novox/mesh-controller/internal/token 1.014s
```
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on novox as build-1791562183549708731 (builds --log build-1791562183549708731).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 54 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T16:12:14Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T16:12:14Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.049s
ok github.com/novox/mesh-controller/cmd/mesh-controller 235.482s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.024s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.031s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.021s
ok github.com/novox/mesh-controller/examples/route-proxy 1.135s
ok github.com/novox/mesh-controller/internal/artifacts 1.057s
ok github.com/novox/mesh-controller/internal/broker 2.883s
ok github.com/novox/mesh-controller/internal/builder 2.258s
ok github.com/novox/mesh-controller/internal/catalogue 5.138s
ok github.com/novox/mesh-controller/internal/conditions 2.568s
ok github.com/novox/mesh-controller/internal/envfile 1.027s
ok github.com/novox/mesh-controller/internal/facts 1.035s
ok github.com/novox/mesh-controller/internal/identity 4.857s
ok github.com/novox/mesh-controller/internal/inventory 92.708s
ok github.com/novox/mesh-controller/internal/lease 17.683s
ok github.com/novox/mesh-controller/internal/licences 4.359s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.010s
ok github.com/novox/mesh-controller/internal/link 54.916s
ok github.com/novox/mesh-controller/internal/lint 2.199s
ok github.com/novox/mesh-controller/internal/outward 1.034s
ok github.com/novox/mesh-controller/internal/overlay 1.023s
ok github.com/novox/mesh-controller/internal/secrets 1.444s
ok github.com/novox/mesh-controller/internal/store 3.314s
ok github.com/novox/mesh-controller/internal/testbus 1.180s
ok github.com/novox/mesh-controller/internal/token 1.014s
**Merge check** at `42e7592d`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on novox as `build-1791562183549708731` (`builds --log build-1791562183549708731`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 54 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T16:12:14Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T16:12:14Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.049s
ok github.com/novox/mesh-controller/cmd/mesh-controller 235.482s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.024s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.031s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.021s
ok github.com/novox/mesh-controller/examples/route-proxy 1.135s
ok github.com/novox/mesh-controller/internal/artifacts 1.057s
ok github.com/novox/mesh-controller/internal/broker 2.883s
ok github.com/novox/mesh-controller/internal/builder 2.258s
ok github.com/novox/mesh-controller/internal/catalogue 5.138s
ok github.com/novox/mesh-controller/internal/conditions 2.568s
ok github.com/novox/mesh-controller/internal/envfile 1.027s
ok github.com/novox/mesh-controller/internal/facts 1.035s
ok github.com/novox/mesh-controller/internal/identity 4.857s
ok github.com/novox/mesh-controller/internal/inventory 92.708s
ok github.com/novox/mesh-controller/internal/lease 17.683s
ok github.com/novox/mesh-controller/internal/licences 4.359s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.010s
ok github.com/novox/mesh-controller/internal/link 54.916s
ok github.com/novox/mesh-controller/internal/lint 2.199s
ok github.com/novox/mesh-controller/internal/outward 1.034s
ok github.com/novox/mesh-controller/internal/overlay 1.023s
ok github.com/novox/mesh-controller/internal/secrets 1.444s
ok github.com/novox/mesh-controller/internal/store 3.314s
ok github.com/novox/mesh-controller/internal/testbus 1.180s
ok github.com/novox/mesh-controller/internal/token 1.014s
```
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.
Registers the fix of hq issue 353 (pull request on hq to follow). Do not merge without review.
Measured on the control node, 2026-10-09 (local times, the controller's journal, process 657383):
asksSeatOfcomposes it from a holder ofoperator-channelthat is assigned, and none was.routerHeresaid yes) and the bus refusedmesh.seat.operator-channel.accept.ask.mesh-controlleron connection [510888]: seven refusals until 17:56:05, each followed by "the operator could not be asked about machine.shanks.units: context deadline exceeded".bus.controller.refusedstays open for an hour after the last refusal (S9'sadvisoryQuiet) and clears by itself at about 18:56.Cause. The controller's grant to ask is composed from the router's assignment and reaches the bus only when the bus's machine is next pushed. Between
assignandpush— and on any push of that machine made while the router is unassigned — the record says a router is here and the bus refuses every ask. The composition is right (the grant follows the holder, as ADR 0259 §3 says); the asker trusted the record before the bus held it.Fix. The asker judges, as a push does (
brokerBehind), whether the machine holding the bus was last sent the user list composed now. While it was not: nothing is published, it is said once, and the conditions that need the operator are raised asasks-undeliverednaming what carries the grant ("push novoxcarries it"). Judged at most every 30 s, because composing the list resolves the bus's machine whole.Tests.
TestNothingIsAskedWhileTheBusLacksTheControllersGrant: nothing asked while the bus lacks the grant, said once, raised as undelivered with the push named, asked once the bus holds it, the condition cleared. Before the fix the asker has no such gate, so the test does not compile against it (the field it drives is the fix).sh merge-check.shruns locally against a throwaway store; its verdict and the forge's are read before merging (issue 341: the branch is on main's head, so the head is the merge result).Delivery
novox/mesh-controller@0c8c9ffae990— delivered since 2026-10-09T17:49:53ZDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.42e7592ddfto0c8c9ffae9Merge check at
0c8c9ffamesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791562733804018506(builds --log build-1791562733804018506).Merge check at
42e7592dmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on novox as
build-1791562183549708731(builds --log build-1791562183549708731).