Ask a seat once more when the controller refused as handing over (hq issue 289) #20

Merged

mesh-admin merged 1 commits from fix/a-verb-survives-the-handover into main 2026-10-07 00:40:21 +00:00

Conversation 2 Commits 1 Files Changed 2

+106 -6

mesh-admin commented 2026-10-07 00:25:17 +00:00

Contributor

Copy Link

Copy Source

novox/hq issue 289. A controller that is being replaced now refuses a call it cannot serve with {"error": …, "retry": "handing-over"}, and the controller after it answers the same call (mesh-controller PR on the same branch name).

bus.Conn.Ask is used by the console, callTool and a module's AskAs. On that mark it waits HandoverPause (3s, which covers the supervisor's restart) and asks once more. An unmarked refusal is final, as before. A second handover refusal is reported ("asked twice … both times refused as a handover") and is not asked a third time.

Test: TestAHandoverRefusalIsAskedOnceMore covers all three cases on a bus of its own (meshtest.URL).

mesh-controller check-here: merge-gate PASS (4 of 4 compose), repo-check PASS. internal/console and internal/runtime are skipped there, as always (they need node and @novox/mesh-sdk). The change is in internal/bus, which is tested.

novox/hq issue 289. A controller that is being replaced now refuses a call it cannot serve with `{"error": …, "retry": "handing-over"}`, and the controller after it answers the same call (mesh-controller PR on the same branch name). `bus.Conn.Ask` is used by the console, `callTool` and a module's `AskAs`. On that mark it waits `HandoverPause` (3s, which covers the supervisor's restart) and asks once more. An unmarked refusal is final, as before. A second handover refusal is reported ("asked twice … both times refused as a handover") and is not asked a third time. Test: `TestAHandoverRefusalIsAskedOnceMore` covers all three cases on a bus of its own (meshtest.URL). `mesh-controller check-here`: merge-gate PASS (4 of 4 compose), repo-check PASS. internal/console and internal/runtime are skipped there, as always (they need node and @novox/mesh-sdk). The change is in internal/bus, which is tested.

mesh-admin added 1 commit 2026-10-07 00:25:17 +00:00

Ask a seat once more when the controller refused as handing over (hq issue 289) ... 2f045e042f

A controller being replaced refuses a call it cannot serve, marked retry:
handing-over; the one after it answers the same call.

mesh-admin commented 2026-10-07 00:25:19 +00:00

Author

Contributor

Copy Link

Copy Source

Delivery novox/mesh-tools@2f045e042f25 — delivered since 2026-10-07T00:44:03Z

Delivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step

• tier 0: mesh-tools, node-tools
• ace: receives node-tools
• g14: receives node-tools
• novox: receives node-tools
• shanks: receives node-tools
• node-tools provides mcp-endpoint: its consumers are sent again after it

Group fix/a-verb-survives-the-handover, in order:

• novox/mesh-controller@9409bcec4b before novox/mesh-host@4b23bed325: built by
• novox/mesh-controller@9409bcec4b before novox/mesh-tools@2f045e042f: built by
• novox/mesh-host@4b23bed325 before novox/mesh-controller@9409bcec4b: engine before controller

Machines

• mesh-tools on every machine running it: sent
• node-tools on ace: passed — healthy 3 times over 2m17s
• node-tools on the rest running it: sent

Transitions

• 2026-10-07 00:27 (new) → proposed (announced): novox/mesh-tools#20's head announced
• 2026-10-07 00:30 proposed → checked (checked): the verdict names this commit
• 2026-10-07 00:30 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-07 00:40 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
• 2026-10-07 00:40 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-07 00:44 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-tools@2f045e042f25` — **delivered** since 2026-10-07T00:44:03Z **Delivery plan** — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step - tier 0: mesh-tools, node-tools - ace: receives node-tools - g14: receives node-tools - novox: receives node-tools - shanks: receives node-tools - node-tools provides mcp-endpoint: its consumers are sent again after it **Group** `fix/a-verb-survives-the-handover`, in order: - novox/mesh-controller@9409bcec4b38 before novox/mesh-host@4b23bed3251b: built by - novox/mesh-controller@9409bcec4b38 before novox/mesh-tools@2f045e042f25: built by - novox/mesh-host@4b23bed3251b before novox/mesh-controller@9409bcec4b38: engine before controller **Machines** - mesh-tools on every machine running it: sent - node-tools on ace: passed — healthy 3 times over 2m17s - node-tools on the rest running it: sent **Transitions** - 2026-10-07 00:27 (new) → proposed (announced): novox/mesh-tools#20's head announced - 2026-10-07 00:30 proposed → checked (checked): the verdict names this commit - 2026-10-07 00:30 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-07 00:40 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-07 00:40 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-07 00:44 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-admin commented 2026-10-07 00:30:05 +00:00

Author

Contributor

Copy Link

Copy Source

Merge check at 2f045e04

• mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)
• mesh/repo-check: PASS — its merge-check.sh passed

Change plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step

• tier 0: mesh-tools, node-tools
• ace: receives node-tools
• g14: receives node-tools
• novox: receives node-tools
• shanks: receives node-tools
• node-tools provides mcp-endpoint: its consumers are sent again after it

Run by the build seat on shanks as build-1791332873846410259 (builds --log build-1791332873846410259).

--- the gate: mesh-tools, node-tools
mesh-tools: ok
node-tools: ok, invokes every tool
2 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-07T00:21:01Z 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-07T00:21:01Z

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-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 2 module(s) in 1 tier(s): mesh-tools, node-tools
--- its merge-check.sh (go toolchain)
NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk
?   	github.com/novox/mesh-tools/node-tools/cmd/node-tools	[no test files]
ok  	github.com/novox/mesh-tools/node-tools/internal/alive	1.190s
ok  	github.com/novox/mesh-tools/node-tools/internal/announce	4.368s
ok  	github.com/novox/mesh-tools/node-tools/internal/bus	1.367s
ok  	github.com/novox/mesh-tools/node-tools/internal/launch	1.045s
ok  	github.com/novox/mesh-tools/node-tools/internal/meshtest	1.129s
?   	github.com/novox/mesh-tools/node-tools/internal/wire	[no test files]
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry

**Merge check** at `2f045e04` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Change plan** — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step - tier 0: mesh-tools, node-tools - ace: receives node-tools - g14: receives node-tools - novox: receives node-tools - shanks: receives node-tools - node-tools provides mcp-endpoint: its consumers are sent again after it Run by the build seat on shanks as `build-1791332873846410259` (`builds --log build-1791332873846410259`). ``` --- the gate: mesh-tools, node-tools mesh-tools: ok node-tools: ok, invokes every tool 2 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-07T00:21:01Z 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-07T00:21:01Z 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-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 2 module(s) in 1 tier(s): mesh-tools, node-tools --- its merge-check.sh (go toolchain) NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk ? github.com/novox/mesh-tools/node-tools/cmd/node-tools [no test files] ok github.com/novox/mesh-tools/node-tools/internal/alive 1.190s ok github.com/novox/mesh-tools/node-tools/internal/announce 4.368s ok github.com/novox/mesh-tools/node-tools/internal/bus 1.367s ok github.com/novox/mesh-tools/node-tools/internal/launch 1.045s ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.129s ? github.com/novox/mesh-tools/node-tools/internal/wire [no test files] NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry ```

mesh-admin merged commit 26a58c7a79 into main 2026-10-07 00:40:21 +00:00

mesh-admin deleted branch fix/a-verb-survives-the-handover 2026-10-07 00:40:21 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

mesh/ready

Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-tools#20