Add the replay of issue 331 (R331) #58

2026-10-08T15:11:10Z

mesh-admin commented

2026-10-08 15:11:10 +00:00

Adds internal/link/replay331_test.go, TestReplay331, the replay mesh-lab's R331 lays over the commit before #57's fix (hq issue 331, ADR 0237).

It uses only what the node-engine had before the fix. A NATS link with no connection under it is attached to the queue, and a tool check must reach the link and fail there, never stop at the queue as "no link to the bus is open". No bus is needed.

Proved with go run ./replays/cmd/prove R331 from the mesh-lab branch, with R331's HomeRef set to 5684a45 (this PR's head):

R331 (issue 331): PROVED — before its fix fails, on its fix passes
  before: replay331_test.go:23: a tool check on the attached NATS link was refused as no link: no link to the bus is open

merge-check.sh passes locally. The registration is in mesh-lab's PR for R331.

Adds `internal/link/replay331_test.go`, `TestReplay331`, the replay mesh-lab's R331 lays over the commit before #57's fix (hq issue 331, ADR 0237). It uses only what the node-engine had before the fix. A NATS link with no connection under it is attached to the queue, and a tool check must reach the link and fail there, never stop at the queue as "no link to the bus is open". No bus is needed. Proved with `go run ./replays/cmd/prove R331` from the mesh-lab branch, with R331's `HomeRef` set to 5684a45 (this PR's head): ``` R331 (issue 331): PROVED — before its fix fails, on its fix passes before: replay331_test.go:23: a tool check on the attached NATS link was refused as no link: no link to the bus is open ``` `merge-check.sh` passes locally. The registration is in mesh-lab's PR for R331.

mesh-admin added 1 commit 2026-10-08 15:11:11 +00:00

Add the replay of issue 331, so a tool check refused as no link fails before a merge

mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)

Details

mesh/repo-check pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

mesh/delivery-group group replays/331-a-tool-check-on-the-live-link merged: every member is merged

Details

5684a4579d

Written with only what the node-engine had before its fix, so mesh-lab's prover can
lay it over the commit before (R331).

mesh-admin commented

2026-10-08 15:11:27 +00:00

Delivery novox/mesh-host@5684a4579d92 — delivered since 2026-10-08T15:21:00Z

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

tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host

Group replays/331-a-tool-check-on-the-live-link, in order: novox/mesh-host@5684a4579d → novox/mesh-lab@3a3317b487

composed together: pass — every machine composes with the change as it did without (4 of 4 compose)

Machines

mesh-host on ace: passed — healthy 3 times over 2m19s
mesh-host on the rest running it: sent

Transitions

2026-10-08 15:11 (new) → proposed (announced): novox/mesh-host#58's head announced
2026-10-08 15:14 proposed → checked (checked): the verdict names this commit
2026-10-08 15:14 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 15:17 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 15:17 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 15:21 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.

**Delivery** `novox/mesh-host@5684a4579d92` — **delivered** since 2026-10-08T15:21:00Z **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host **Group** `replays/331-a-tool-check-on-the-live-link`, in order: novox/mesh-host@5684a4579d92 → novox/mesh-lab@3a3317b48749 - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **Machines** - mesh-host on ace: passed — healthy 3 times over 2m19s - mesh-host on the rest running it: sent **Transitions** - 2026-10-08 15:11 (new) → proposed (announced): novox/mesh-host#58's head announced - 2026-10-08 15:14 proposed → checked (checked): the verdict names this commit - 2026-10-08 15:14 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 15:17 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 15:17 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 15:21 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:14:23 +00:00

Merge check at 5684a457

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

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

tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host

Run by the build seat on novox as build-1791472283789095250 (builds --log build-1791472283789095250).

--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T15:09:23Z 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:09:23Z

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 1 module(s) in 1 tier(s): mesh-host
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-host/cmd/mesh-bootstrap	1.017s
ok  	github.com/novox/mesh-host/cmd/mesh-host	6.666s
ok  	github.com/novox/mesh-host/examples	1.025s
ok  	github.com/novox/mesh-host/internal/accounts	1.034s
ok  	github.com/novox/mesh-host/internal/apply	25.479s
ok  	github.com/novox/mesh-host/internal/bootstrap	3.099s
ok  	github.com/novox/mesh-host/internal/bundle	1.018s
ok  	github.com/novox/mesh-host/internal/declaration	1.059s
ok  	github.com/novox/mesh-host/internal/firewall	1.852s
ok  	github.com/novox/mesh-host/internal/identity	1.657s
ok  	github.com/novox/mesh-host/internal/image	1.020s
ok  	github.com/novox/mesh-host/internal/inventory	1.026s
ok  	github.com/novox/mesh-host/internal/link	10.349s
ok  	github.com/novox/mesh-host/internal/liveness	2.419s
ok  	github.com/novox/mesh-host/internal/network	1.041s
ok  	github.com/novox/mesh-host/internal/outward	1.018s
ok  	github.com/novox/mesh-host/internal/profile	1.487s
ok  	github.com/novox/mesh-host/internal/reachable	1.013s
ok  	github.com/novox/mesh-host/internal/store	2.108s
ok  	github.com/novox/mesh-host/internal/system	1.011s
ok  	github.com/novox/mesh-host/internal/tunnel	1.016s
ok  	github.com/novox/mesh-host/internal/units	1.008s
ok  	github.com/novox/mesh-host/internal/upgrade	1.607s
ok  	github.com/novox/mesh-host/internal/witness	32.034s
ok  	github.com/novox/mesh-host/packaging	1.011s
ok  	github.com/novox/mesh-host/validate	1.007s

**Merge check** at `5684a457` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host Run by the build seat on novox as `build-1791472283789095250` (`builds --log build-1791472283789095250`). ``` --- the gate: mesh-host mesh-host: ok long-running resources without health: 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T15:09:23Z 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:09:23Z 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 1 module(s) in 1 tier(s): mesh-host --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.017s ok github.com/novox/mesh-host/cmd/mesh-host 6.666s ok github.com/novox/mesh-host/examples 1.025s ok github.com/novox/mesh-host/internal/accounts 1.034s ok github.com/novox/mesh-host/internal/apply 25.479s ok github.com/novox/mesh-host/internal/bootstrap 3.099s ok github.com/novox/mesh-host/internal/bundle 1.018s ok github.com/novox/mesh-host/internal/declaration 1.059s ok github.com/novox/mesh-host/internal/firewall 1.852s ok github.com/novox/mesh-host/internal/identity 1.657s ok github.com/novox/mesh-host/internal/image 1.020s ok github.com/novox/mesh-host/internal/inventory 1.026s ok github.com/novox/mesh-host/internal/link 10.349s ok github.com/novox/mesh-host/internal/liveness 2.419s ok github.com/novox/mesh-host/internal/network 1.041s ok github.com/novox/mesh-host/internal/outward 1.018s ok github.com/novox/mesh-host/internal/profile 1.487s ok github.com/novox/mesh-host/internal/reachable 1.013s ok github.com/novox/mesh-host/internal/store 2.108s ok github.com/novox/mesh-host/internal/system 1.011s ok github.com/novox/mesh-host/internal/tunnel 1.016s ok github.com/novox/mesh-host/internal/units 1.008s ok github.com/novox/mesh-host/internal/upgrade 1.607s ok github.com/novox/mesh-host/internal/witness 32.034s ok github.com/novox/mesh-host/packaging 1.011s ok github.com/novox/mesh-host/validate 1.007s ```

mesh-admin merged commit e813391dcf into main

2026-10-08 15:17:21 +00:00

mesh-admin deleted branch replays/331-a-tool-check-on-the-live-link

2026-10-08 15:17:21 +00:00

jschoubben referenced this issue from a commit

2026-10-21 12:27:12 +00:00

Pass a container's groups to the runtime as supplementary groups and report container-groups (issues 1637, ADR 0480 clause 7)

jschoubben referenced this issue from a commit

2026-10-21 13:03:29 +00:00

Pin mesh-sdk to main at the merge of #59 (carries #58's groups field)

jschoubben referenced this issue from a commit

2026-10-21 13:34:59 +00:00