novox/mesh-controller
Archived
9
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Keep what a consumer gives up on until a person delivers it again or drops it (hq issue 330, ADR 0264) #159

Merged
mesh-admin merged 2 commits from fix/330-a-message-given-up-on-is-kept into main 2026-10-08 19:07:34 +00:00
Conversation 5 Commits 2 Files Changed 26
+1454 -28
mesh-admin commented 2026-10-08 15:37:12 +00:00
Contributor
Copy Link
Copy Source

Design 25 promised a dead-letter stream that did not exist (hq issue 330). This builds it, NATS-native, as hq ADR 0264 decides:

  • DEAD_LETTER_NOTICES captures the server's $JS.EVENT.ADVISORY.CONSUMER.MAX_DELIVERIES.> advisory as a work queue, so a notice said while no controller listens is not lost. The serving controller's consumer on it fetches the given-up message by stream sequence and keeps a copy.
  • DEAD_LETTERS (mesh.events.dead.<stream>.<consumer>) keeps the copy with its consumer, stream, subject, sequence, deliveries, when it was given up and first published; no age, 256 MiB, refuses new when full; one copy per message (msg id <stream>.<consumer>.<seq>).
  • Delivered again to its consumer alone: EVENTS takes mesh.again.> and every consumer on it filters its own mesh.again.<consumer>.>; the runtimes read the same key from it. An ask goes back on its seat's subject.
  • Verb dead-letters (in-process, on the serving controller's connection): list, one whole by id, deliver or drop with why, recorded in the hand-act log as a person's decision.
  • max-deliveries condition open per consumer while DEAD_LETTERS holds its messages, in plain words: "Needs you: deliver them again or drop them, from the mesh MCP server." A copy that could not be made is its own condition (not-kept).
  • The false "dead-letters" comments in streams.go and derived.go are corrected; writers table and grants extended (golden updated).

Replay: internal/link/replay330_test.go (R330 in mesh-lab), proved: fails on a5f53ef, passes on 75e567a.

merge-check.sh: passed locally (race detector on).

Delivery group: fix/330-a-message-given-up-on-is-kept with mesh-tools, mesh-lab and hq.

Design 25 promised a dead-letter stream that did not exist (hq issue 330). This builds it, NATS-native, as hq ADR 0264 decides: - **DEAD_LETTER_NOTICES** captures the server's `$JS.EVENT.ADVISORY.CONSUMER.MAX_DELIVERIES.>` advisory as a work queue, so a notice said while no controller listens is not lost. The serving controller's consumer on it fetches the given-up message by stream sequence and keeps a copy. - **DEAD_LETTERS** (`mesh.events.dead.<stream>.<consumer>`) keeps the copy with its consumer, stream, subject, sequence, deliveries, when it was given up and first published; no age, 256 MiB, refuses new when full; one copy per message (msg id `<stream>.<consumer>.<seq>`). - **Delivered again to its consumer alone**: EVENTS takes `mesh.again.>` and every consumer on it filters its own `mesh.again.<consumer>.>`; the runtimes read the same key from it. An ask goes back on its seat's subject. - **Verb `dead-letters`** (in-process, on the serving controller's connection): list, one whole by id, `deliver` or `drop` with `why`, recorded in the hand-act log as a person's decision. - **`max-deliveries` condition** open per consumer while DEAD_LETTERS holds its messages, in plain words: "Needs you: deliver them again or drop them, from the mesh MCP server." A copy that could not be made is its own condition (`not-kept`). - The false "dead-letters" comments in streams.go and derived.go are corrected; writers table and grants extended (golden updated). Replay: `internal/link/replay330_test.go` (R330 in mesh-lab), proved: fails on a5f53ef, passes on 75e567a. merge-check.sh: passed locally (race detector on). Delivery group: `fix/330-a-message-given-up-on-is-kept` with mesh-tools, mesh-lab and hq.
mesh-admin commented 2026-10-08 15:37:48 +00:00
Author
Contributor
Copy Link
Copy Source

Delivery novox/mesh-controller@909062e7294d — delivered since 2026-10-08T19:23:31Z

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

Group fix/330-a-message-given-up-on-is-kept, in order: novox/hq@26ff767a7b → novox/mesh-controller@909062e729 → novox/mesh-host@a31659ed03 → novox/mesh-lab@54db7c3458 → novox/mesh-tools@c401bbff2d

Machines

  • mesh-controller on novox: passed — healthy 3 times over 3m43s
  • mesh-controller on the rest running it: sent
  • build-agent on ace: passed — healthy 3 times over 3m46s
  • build-agent on the rest running it: sent
  • route-proxy on ace: passed — healthy 3 times over 3m40s
  • route-proxy on the rest running it: sent

Transitions

  • 2026-10-08 16:38 (new) → proposed (announced): novox/mesh-controller#159's head announced
  • 2026-10-08 16:44 proposed → checked (checked): the verdict names this commit
  • 2026-10-08 16:44 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
  • 2026-10-08 18:21 rejected → proposed (recheck): mesh-host #60 merged; its installer user list now carries #159's grants
  • 2026-10-08 18:26 proposed → checked (checked): the verdict names this commit
  • 2026-10-08 18:26 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
  • 2026-10-08 18:31 rejected → proposed (recheck): the recheck at 18:21Z cloned mesh-host at e813391, the build current then; mesh-host 29a7de7 (with #60's user list) registered at 18:21Z, so the installer-list test read the old list. Checked again against the build now current.
  • 2026-10-08 18:35 proposed → checked (checked): the verdict names this commit
  • 2026-10-08 18:35 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-08 19:07 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-08 19:07 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-08 19:23 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@909062e7294d` — **delivered** since 2026-10-08T19:23:31Z **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 **Group** `fix/330-a-message-given-up-on-is-kept`, in order: novox/hq@26ff767a7b89 → novox/mesh-controller@909062e7294d → novox/mesh-host@a31659ed0328 → novox/mesh-lab@54db7c3458f7 → novox/mesh-tools@c401bbff2d7a - novox/mesh-controller@909062e7294d before novox/mesh-host@a31659ed0328: built by, over engine before controller - novox/mesh-controller@909062e7294d before novox/mesh-tools@c401bbff2d7a: built by **Machines** - mesh-controller on novox: passed — healthy 3 times over 3m43s - mesh-controller on the rest running it: sent - build-agent on ace: passed — healthy 3 times over 3m46s - build-agent on the rest running it: sent - route-proxy on ace: passed — healthy 3 times over 3m40s - route-proxy on the rest running it: sent **Transitions** - 2026-10-08 16:38 (new) → proposed (announced): novox/mesh-controller#159's head announced - 2026-10-08 16:44 proposed → checked (checked): the verdict names this commit - 2026-10-08 16:44 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed - 2026-10-08 18:21 rejected → proposed (recheck): mesh-host #60 merged; its installer user list now carries #159's grants - 2026-10-08 18:26 proposed → checked (checked): the verdict names this commit - 2026-10-08 18:26 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed - 2026-10-08 18:31 rejected → proposed (recheck): the recheck at 18:21Z cloned mesh-host at e813391, the build current then; mesh-host 29a7de7 (with #60's user list) registered at 18:21Z, so the installer-list test read the old list. Checked again against the build now current. - 2026-10-08 18:35 proposed → checked (checked): the verdict names this commit - 2026-10-08 18:35 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 19:07 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-08 19:07 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-08 19:23 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-08 15:42:55 +00:00
Author
Contributor
Copy Link
Copy Source

Merge check at 75e567af

  • 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: FAIL — its merge-check.sh failed: --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.63s)

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 ace as build-1791473864542159569 (builds --log build-1791473864542159569).

--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 52 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
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-08T15:33:40Z 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-08T15:33:40Z

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.047s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	180.490s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.014s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.020s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.016s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.135s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.058s
--- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.63s)
    genesis_template_test.go:37: the installer's user list does not let the controller publish [$JS.ACK.DEAD_LETTER_NOTICES.controller.> mesh.again.> mesh.events.dead.> mesh.seat.*.accept.>] — it would come up and be refused on the first thing it tried
FAIL
FAIL	github.com/novox/mesh-controller/internal/broker	1.565s
ok  	github.com/novox/mesh-controller/internal/builder	2.142s
ok  	github.com/novox/mesh-controller/internal/catalogue	4.312s
ok  	github.com/novox/mesh-controller/internal/conditions	2.245s
ok  	github.com/novox/mesh-controller/internal/envfile	1.062s
ok  	github.com/novox/mesh-controller/internal/facts	1.069s
ok  	github.com/novox/mesh-controller/internal/identity	4.632s
ok  	github.com/novox/mesh-controller/internal/inventory	79.019s
ok  	github.com/novox/mesh-controller/internal/lease	17.743s
ok  	github.com/novox/mesh-controller/internal/licences	4.306s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.060s
ok  	github.com/novox/mesh-controller/internal/link	51.270s
ok  	github.com/novox/mesh-controller/internal/lint	2.031s
ok  	github.com/novox/mesh-controller/internal/outward	1.088s
ok  	github.com/novox/mesh-controller/internal/overlay	1.080s
ok  	github.com/novox/mesh-controller/internal/secrets	1.454s
ok  	github.com/novox/mesh-controller/internal/store	3.519s
ok  	github.com/novox/mesh-controller/internal/testbus	1.235s
ok  	github.com/novox/mesh-controller/internal/token	1.020s
FAIL
**Merge check** at `75e567af` - `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`: **FAIL** — its merge-check.sh failed: --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.63s) **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 ace as `build-1791473864542159569` (`builds --log build-1791473864542159569`). ``` --- the gate: build-agent, mesh-controller, route-proxy mesh-controller: ok, 52 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 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-08T15:33:40Z 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-08T15:33:40Z 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.047s ok github.com/novox/mesh-controller/cmd/mesh-controller 180.490s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.014s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.020s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.016s ok github.com/novox/mesh-controller/examples/route-proxy 1.135s ok github.com/novox/mesh-controller/internal/artifacts 1.058s --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.63s) genesis_template_test.go:37: the installer's user list does not let the controller publish [$JS.ACK.DEAD_LETTER_NOTICES.controller.> mesh.again.> mesh.events.dead.> mesh.seat.*.accept.>] — it would come up and be refused on the first thing it tried FAIL FAIL github.com/novox/mesh-controller/internal/broker 1.565s ok github.com/novox/mesh-controller/internal/builder 2.142s ok github.com/novox/mesh-controller/internal/catalogue 4.312s ok github.com/novox/mesh-controller/internal/conditions 2.245s ok github.com/novox/mesh-controller/internal/envfile 1.062s ok github.com/novox/mesh-controller/internal/facts 1.069s ok github.com/novox/mesh-controller/internal/identity 4.632s ok github.com/novox/mesh-controller/internal/inventory 79.019s ok github.com/novox/mesh-controller/internal/lease 17.743s ok github.com/novox/mesh-controller/internal/licences 4.306s ok github.com/novox/mesh-controller/internal/licences/adapters 1.060s ok github.com/novox/mesh-controller/internal/link 51.270s ok github.com/novox/mesh-controller/internal/lint 2.031s ok github.com/novox/mesh-controller/internal/outward 1.088s ok github.com/novox/mesh-controller/internal/overlay 1.080s ok github.com/novox/mesh-controller/internal/secrets 1.454s ok github.com/novox/mesh-controller/internal/store 3.519s ok github.com/novox/mesh-controller/internal/testbus 1.235s ok github.com/novox/mesh-controller/internal/token 1.020s FAIL ```
jschoubben added 2 commits 2026-10-08 16:38:14 +00:00
Keep what a consumer gives up on until a person delivers it again or drops it 826dcb91b1 
Design 25 promised a dead-letter stream that did not exist: a message a
consumer gave up on stayed only in its source, which drops it after a week,
and its condition cleared when the advisories stopped (hq issue 330, ADR 0264).
Deliver a dead letter again only where it is received, and never stop serving for the notices
mesh/delivery delivered
Details
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…
Details
mesh/repo-check pass: its merge-check.sh passed
Details
mesh/delivery-group group fix/330-a-message-given-up-on-is-kept merged: every member is merged
Details
909062e729 
A dead letter was let go as delivered even when its consumer did not filter
its again subject; seat asks needed a grant over every seat's queue and left
the original stuck; a notices bind failure stopped the controller (review).
jschoubben force-pushed fix/330-a-message-given-up-on-is-kept from 75e567af1e to 909062e729 2026-10-08 16:38:14 +00:00 Compare
mesh-admin commented 2026-10-08 16:44:31 +00:00
Author
Contributor
Copy Link
Copy Source

Merge check at 909062e7

  • 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: FAIL — its merge-check.sh failed: --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.66s)

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 ace as build-1791477503522398428 (builds --log build-1791477503522398428).

--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 52 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
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-08T16:26:42Z 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-08T16:26:42Z

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	175.095s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.013s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.019s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.110s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.246s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.063s
--- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.66s)
    genesis_template_test.go:37: the installer's user list does not let the controller publish [$JS.ACK.DEAD_LETTER_NOTICES.controller.> mesh.again.> mesh.events.dead.>] — it would come up and be refused on the first thing it tried
FAIL
FAIL	github.com/novox/mesh-controller/internal/broker	1.561s
ok  	github.com/novox/mesh-controller/internal/builder	2.041s
ok  	github.com/novox/mesh-controller/internal/catalogue	4.390s
ok  	github.com/novox/mesh-controller/internal/conditions	2.309s
ok  	github.com/novox/mesh-controller/internal/envfile	1.068s
ok  	github.com/novox/mesh-controller/internal/facts	1.072s
ok  	github.com/novox/mesh-controller/internal/identity	4.436s
ok  	github.com/novox/mesh-controller/internal/inventory	77.872s
ok  	github.com/novox/mesh-controller/internal/lease	17.765s
ok  	github.com/novox/mesh-controller/internal/licences	4.023s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.067s
ok  	github.com/novox/mesh-controller/internal/link	52.361s
ok  	github.com/novox/mesh-controller/internal/lint	2.125s
ok  	github.com/novox/mesh-controller/internal/outward	1.102s
ok  	github.com/novox/mesh-controller/internal/overlay	1.087s
ok  	github.com/novox/mesh-controller/internal/secrets	1.513s
ok  	github.com/novox/mesh-controller/internal/store	3.481s
ok  	github.com/novox/mesh-controller/internal/testbus	1.262s
ok  	github.com/novox/mesh-controller/internal/token	1.017s
FAIL
**Merge check** at `909062e7` - `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`: **FAIL** — its merge-check.sh failed: --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.66s) **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 ace as `build-1791477503522398428` (`builds --log build-1791477503522398428`). ``` --- the gate: build-agent, mesh-controller, route-proxy mesh-controller: ok, 52 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 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-08T16:26:42Z 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-08T16:26:42Z 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 175.095s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.013s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.019s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.110s ok github.com/novox/mesh-controller/examples/route-proxy 1.246s ok github.com/novox/mesh-controller/internal/artifacts 1.063s --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.66s) genesis_template_test.go:37: the installer's user list does not let the controller publish [$JS.ACK.DEAD_LETTER_NOTICES.controller.> mesh.again.> mesh.events.dead.>] — it would come up and be refused on the first thing it tried FAIL FAIL github.com/novox/mesh-controller/internal/broker 1.561s ok github.com/novox/mesh-controller/internal/builder 2.041s ok github.com/novox/mesh-controller/internal/catalogue 4.390s ok github.com/novox/mesh-controller/internal/conditions 2.309s ok github.com/novox/mesh-controller/internal/envfile 1.068s ok github.com/novox/mesh-controller/internal/facts 1.072s ok github.com/novox/mesh-controller/internal/identity 4.436s ok github.com/novox/mesh-controller/internal/inventory 77.872s ok github.com/novox/mesh-controller/internal/lease 17.765s ok github.com/novox/mesh-controller/internal/licences 4.023s ok github.com/novox/mesh-controller/internal/licences/adapters 1.067s ok github.com/novox/mesh-controller/internal/link 52.361s ok github.com/novox/mesh-controller/internal/lint 2.125s ok github.com/novox/mesh-controller/internal/outward 1.102s ok github.com/novox/mesh-controller/internal/overlay 1.087s ok github.com/novox/mesh-controller/internal/secrets 1.513s ok github.com/novox/mesh-controller/internal/store 3.481s ok github.com/novox/mesh-controller/internal/testbus 1.262s ok github.com/novox/mesh-controller/internal/token 1.017s FAIL ```
mesh-admin commented 2026-10-08 18:26:54 +00:00
Author
Contributor
Copy Link
Copy Source

Merge check at 909062e7

  • 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: FAIL — its merge-check.sh failed: --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.73s)

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-1791483677502264801 (builds --log build-1791483677502264801).

--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 52 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
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-08T18:08:48Z 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-08T18:08:48Z

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.035s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	191.597s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.046s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.053s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.044s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.248s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.090s
--- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.73s)
    genesis_template_test.go:37: the installer's user list does not let the controller publish [$JS.ACK.DEAD_LETTER_NOTICES.controller.> mesh.again.> mesh.events.dead.>] — it would come up and be refused on the first thing it tried
FAIL
FAIL	github.com/novox/mesh-controller/internal/broker	7.064s
ok  	github.com/novox/mesh-controller/internal/builder	8.266s
ok  	github.com/novox/mesh-controller/internal/catalogue	4.744s
ok  	github.com/novox/mesh-controller/internal/conditions	2.233s
ok  	github.com/novox/mesh-controller/internal/envfile	1.055s
ok  	github.com/novox/mesh-controller/internal/facts	1.052s
ok  	github.com/novox/mesh-controller/internal/identity	9.962s
ok  	github.com/novox/mesh-controller/internal/inventory	89.829s
ok  	github.com/novox/mesh-controller/internal/lease	17.774s
ok  	github.com/novox/mesh-controller/internal/licences	9.465s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.046s
ok  	github.com/novox/mesh-controller/internal/link	55.206s
ok  	github.com/novox/mesh-controller/internal/lint	2.191s
ok  	github.com/novox/mesh-controller/internal/outward	1.073s
ok  	github.com/novox/mesh-controller/internal/overlay	1.065s
ok  	github.com/novox/mesh-controller/internal/secrets	1.560s
ok  	github.com/novox/mesh-controller/internal/store	6.627s
ok  	github.com/novox/mesh-controller/internal/testbus	1.231s
ok  	github.com/novox/mesh-controller/internal/token	1.015s
FAIL
**Merge check** at `909062e7` - `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`: **FAIL** — its merge-check.sh failed: --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.73s) **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-1791483677502264801` (`builds --log build-1791483677502264801`). ``` --- the gate: build-agent, mesh-controller, route-proxy mesh-controller: ok, 52 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 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-08T18:08:48Z 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-08T18:08:48Z 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.035s ok github.com/novox/mesh-controller/cmd/mesh-controller 191.597s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.046s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.053s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.044s ok github.com/novox/mesh-controller/examples/route-proxy 1.248s ok github.com/novox/mesh-controller/internal/artifacts 1.090s --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.73s) genesis_template_test.go:37: the installer's user list does not let the controller publish [$JS.ACK.DEAD_LETTER_NOTICES.controller.> mesh.again.> mesh.events.dead.>] — it would come up and be refused on the first thing it tried FAIL FAIL github.com/novox/mesh-controller/internal/broker 7.064s ok github.com/novox/mesh-controller/internal/builder 8.266s ok github.com/novox/mesh-controller/internal/catalogue 4.744s ok github.com/novox/mesh-controller/internal/conditions 2.233s ok github.com/novox/mesh-controller/internal/envfile 1.055s ok github.com/novox/mesh-controller/internal/facts 1.052s ok github.com/novox/mesh-controller/internal/identity 9.962s ok github.com/novox/mesh-controller/internal/inventory 89.829s ok github.com/novox/mesh-controller/internal/lease 17.774s ok github.com/novox/mesh-controller/internal/licences 9.465s ok github.com/novox/mesh-controller/internal/licences/adapters 1.046s ok github.com/novox/mesh-controller/internal/link 55.206s ok github.com/novox/mesh-controller/internal/lint 2.191s ok github.com/novox/mesh-controller/internal/outward 1.073s ok github.com/novox/mesh-controller/internal/overlay 1.065s ok github.com/novox/mesh-controller/internal/secrets 1.560s ok github.com/novox/mesh-controller/internal/store 6.627s ok github.com/novox/mesh-controller/internal/testbus 1.231s ok github.com/novox/mesh-controller/internal/token 1.015s FAIL ```
mesh-admin commented 2026-10-08 18:35:57 +00:00
Author
Contributor
Copy Link
Copy Source

Merge check at 909062e7

  • 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 ace as build-1791484310077054539 (builds --log build-1791484310077054539).

--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 52 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
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-08T18:28:48Z 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-08T18:28:48Z

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.038s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	161.274s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.014s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.018s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.014s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.111s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.042s
ok  	github.com/novox/mesh-controller/internal/broker	2.479s
ok  	github.com/novox/mesh-controller/internal/builder	1.804s
ok  	github.com/novox/mesh-controller/internal/catalogue	4.034s
ok  	github.com/novox/mesh-controller/internal/conditions	2.175s
ok  	github.com/novox/mesh-controller/internal/envfile	1.056s
ok  	github.com/novox/mesh-controller/internal/facts	1.055s
ok  	github.com/novox/mesh-controller/internal/identity	4.091s
ok  	github.com/novox/mesh-controller/internal/inventory	71.138s
ok  	github.com/novox/mesh-controller/internal/lease	17.693s
ok  	github.com/novox/mesh-controller/internal/licences	3.742s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.050s
ok  	github.com/novox/mesh-controller/internal/link	50.664s
ok  	github.com/novox/mesh-controller/internal/lint	1.948s
ok  	github.com/novox/mesh-controller/internal/outward	1.077s
ok  	github.com/novox/mesh-controller/internal/overlay	1.063s
ok  	github.com/novox/mesh-controller/internal/secrets	1.414s
ok  	github.com/novox/mesh-controller/internal/store	3.280s
ok  	github.com/novox/mesh-controller/internal/testbus	1.177s
ok  	github.com/novox/mesh-controller/internal/token	1.016s
**Merge check** at `909062e7` - `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 ace as `build-1791484310077054539` (`builds --log build-1791484310077054539`). ``` --- the gate: build-agent, mesh-controller, route-proxy mesh-controller: ok, 52 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 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-08T18:28:48Z 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-08T18:28:48Z 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.038s ok github.com/novox/mesh-controller/cmd/mesh-controller 161.274s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.014s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.018s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.014s ok github.com/novox/mesh-controller/examples/route-proxy 1.111s ok github.com/novox/mesh-controller/internal/artifacts 1.042s ok github.com/novox/mesh-controller/internal/broker 2.479s ok github.com/novox/mesh-controller/internal/builder 1.804s ok github.com/novox/mesh-controller/internal/catalogue 4.034s ok github.com/novox/mesh-controller/internal/conditions 2.175s ok github.com/novox/mesh-controller/internal/envfile 1.056s ok github.com/novox/mesh-controller/internal/facts 1.055s ok github.com/novox/mesh-controller/internal/identity 4.091s ok github.com/novox/mesh-controller/internal/inventory 71.138s ok github.com/novox/mesh-controller/internal/lease 17.693s ok github.com/novox/mesh-controller/internal/licences 3.742s ok github.com/novox/mesh-controller/internal/licences/adapters 1.050s ok github.com/novox/mesh-controller/internal/link 50.664s ok github.com/novox/mesh-controller/internal/lint 1.948s ok github.com/novox/mesh-controller/internal/outward 1.077s ok github.com/novox/mesh-controller/internal/overlay 1.063s ok github.com/novox/mesh-controller/internal/secrets 1.414s ok github.com/novox/mesh-controller/internal/store 3.280s ok github.com/novox/mesh-controller/internal/testbus 1.177s ok github.com/novox/mesh-controller/internal/token 1.016s ```
mesh-admin merged commit ca09a07fdf into main 2026-10-08 19:07:34 +00:00
mesh-admin deleted branch fix/330-a-message-given-up-on-is-kept 2026-10-08 19:07:34 +00:00
This repo is archived. You cannot comment on pull requests.
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
Assignees
Clear assignees
agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent
No Assignees
2 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-controller#159