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

Keep a left-out module's provisions and backups, and refuse more identity keys (hq ADR 0262) #162

Merged
mesh-admin merged 2 commits from feat/left-out-keeps-what-it-provides into main 2026-10-08 16:37:43 +00:00
Conversation 3 Commits 2 Files Changed 7
+347 -28
mesh-admin commented 2026-10-08 16:03:55 +00:00
Contributor
Copy Link
Copy Source

Follow-up to #153 from the third review.

  • A second pass reads past an unknown key inside an entry. Each top-level field is decoded alone; where an entry has an unknown key, the one occurrence whose removal moves the strict decoder past it is removed, never a key of the same name another entry knows (if no single removal helps, every occurrence of that key in that field is removed; if nothing helps, the manifest keeps its name and version and is still left out and raised). So a left-out module still provides what it provides, and no consumer is refused mesh-wide for it. The condition's evidence names each key read past (provides[1].x, data.own[0].backup.class).
  • A left-out module's data is still backed up: its data and directories are given to the backup holder on its machine; nothing else of it is declared. The left-out reason and the condition now say what stops (files and services unchanged, contributions to other modules and its open ports) and that its data is still backed up.
  • Name check: adds host-name, user-name, domain-name, nameserver, dns-server(s), gateway, subnet, sender, recipient, contact, certificate; allow-from/deny-from; drops allow and use from the number-or-switch prefixes (allow-hosts, use-host are identities; allow-resize, use-gpu remain preferences).
  • Tests: TestALeftOutModuleStillProvidesWhatItProvides, TestALeftOutModulesDataIsStillBackedUp (fails without the change), the name tables. merge-check.sh passes locally with a test database.

hq: ADR 0262 (#216) already describes this follow-up.

Follow-up to #153 from the third review. - **A second pass reads past an unknown key inside an entry.** Each top-level field is decoded alone; where an entry has an unknown key, the one occurrence whose removal moves the strict decoder past it is removed, never a key of the same name another entry knows (if no single removal helps, every occurrence of that key in that field is removed; if nothing helps, the manifest keeps its name and version and is still left out and raised). So a left-out module still provides what it provides, and no consumer is refused mesh-wide for it. The condition's evidence names each key read past (`provides[1].x`, `data.own[0].backup.class`). - **A left-out module's data is still backed up:** its data and directories are given to the backup holder on its machine; nothing else of it is declared. The left-out reason and the condition now say what stops (files and services unchanged, contributions to other modules and its open ports) and that its data is still backed up. - **Name check:** adds host-name, user-name, domain-name, nameserver, dns-server(s), gateway, subnet, sender, recipient, contact, certificate; `allow-from`/`deny-from`; drops `allow` and `use` from the number-or-switch prefixes (`allow-hosts`, `use-host` are identities; `allow-resize`, `use-gpu` remain preferences). - Tests: `TestALeftOutModuleStillProvidesWhatItProvides`, `TestALeftOutModulesDataIsStillBackedUp` (fails without the change), the name tables. `merge-check.sh` passes locally with a test database. hq: ADR 0262 (#216) already describes this follow-up.
mesh-admin added 1 commit 2026-10-08 16:03:55 +00:00
Keep a left-out module's provisions and backups, and refuse more identity keys (hq ADR 0262)
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 superseded: a newer head of the same pull request
Details
5d47e0bfd6 
A module left out for an unknown key inside an entry lost its whole manifest, so every consumer of what
it provides was refused and its data stopped being copied. Read past only the unknown key, keep its
backup lines, and say in the condition what stops.
mesh-admin commented 2026-10-08 16:04:08 +00:00
Author
Contributor
Copy Link
Copy Source

Delivery novox/mesh-controller@193168e08607 — delivered since 2026-10-08T18:06:36Z

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 3m37s
  • mesh-controller on the rest running it: sent
  • build-agent on ace: passed — healthy 3 times over 3m36s
  • build-agent on the rest running it: sent
  • route-proxy on ace: passed — healthy 3 times over 3m33s
  • route-proxy on the rest running it: sent

Transitions

  • 2026-10-08 16:28 (new) → proposed (announced): novox/mesh-controller#162's head announced
  • 2026-10-08 16:33 proposed → checked (checked): the verdict names this commit
  • 2026-10-08 16:33 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-08 16:37 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 16:37 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 18:06 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@193168e08607` — **delivered** since 2026-10-08T18:06:36Z **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 3m37s - mesh-controller on the rest running it: sent - build-agent on ace: passed — healthy 3 times over 3m36s - build-agent on the rest running it: sent - route-proxy on ace: passed — healthy 3 times over 3m33s - route-proxy on the rest running it: sent **Transitions** - 2026-10-08 16:28 (new) → proposed (announced): novox/mesh-controller#162's head announced - 2026-10-08 16:33 proposed → checked (checked): the verdict names this commit - 2026-10-08 16:33 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 16:37 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 16:37 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 18:06 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 16:09:11 +00:00
Author
Contributor
Copy Link
Copy Source

Merge check at 5d47e0bf

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

--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 51 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T15:57: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-08T15:57:42Z

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	186.852s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.018s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.018s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.013s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.125s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.038s
ok  	github.com/novox/mesh-controller/internal/broker	2.620s
ok  	github.com/novox/mesh-controller/internal/builder	2.067s
ok  	github.com/novox/mesh-controller/internal/catalogue	4.719s
ok  	github.com/novox/mesh-controller/internal/conditions	2.276s
ok  	github.com/novox/mesh-controller/internal/envfile	1.095s
ok  	github.com/novox/mesh-controller/internal/facts	1.060s
ok  	github.com/novox/mesh-controller/internal/identity	4.901s
ok  	github.com/novox/mesh-controller/internal/inventory	86.221s
ok  	github.com/novox/mesh-controller/internal/lease	17.652s
ok  	github.com/novox/mesh-controller/internal/licences	4.391s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.085s
ok  	github.com/novox/mesh-controller/internal/link	48.717s
ok  	github.com/novox/mesh-controller/internal/lint	2.148s
ok  	github.com/novox/mesh-controller/internal/outward	1.087s
ok  	github.com/novox/mesh-controller/internal/overlay	1.103s
ok  	github.com/novox/mesh-controller/internal/secrets	1.512s
ok  	github.com/novox/mesh-controller/internal/store	3.601s
ok  	github.com/novox/mesh-controller/internal/testbus	1.239s
ok  	github.com/novox/mesh-controller/internal/token	1.022s
**Merge check** at `5d47e0bf` - `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-1791475446376858862` (`builds --log build-1791475446376858862`). ``` --- the gate: build-agent, mesh-controller, route-proxy mesh-controller: ok, 51 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T15:57: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-08T15:57:42Z 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 186.852s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.018s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.018s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.013s ok github.com/novox/mesh-controller/examples/route-proxy 1.125s ok github.com/novox/mesh-controller/internal/artifacts 1.038s ok github.com/novox/mesh-controller/internal/broker 2.620s ok github.com/novox/mesh-controller/internal/builder 2.067s ok github.com/novox/mesh-controller/internal/catalogue 4.719s ok github.com/novox/mesh-controller/internal/conditions 2.276s ok github.com/novox/mesh-controller/internal/envfile 1.095s ok github.com/novox/mesh-controller/internal/facts 1.060s ok github.com/novox/mesh-controller/internal/identity 4.901s ok github.com/novox/mesh-controller/internal/inventory 86.221s ok github.com/novox/mesh-controller/internal/lease 17.652s ok github.com/novox/mesh-controller/internal/licences 4.391s ok github.com/novox/mesh-controller/internal/licences/adapters 1.085s ok github.com/novox/mesh-controller/internal/link 48.717s ok github.com/novox/mesh-controller/internal/lint 2.148s ok github.com/novox/mesh-controller/internal/outward 1.087s ok github.com/novox/mesh-controller/internal/overlay 1.103s ok github.com/novox/mesh-controller/internal/secrets 1.512s ok github.com/novox/mesh-controller/internal/store 3.601s ok github.com/novox/mesh-controller/internal/testbus 1.239s ok github.com/novox/mesh-controller/internal/token 1.022s ```
jschoubben added 1 commit 2026-10-08 16:27:56 +00:00
Place a left-out module's backup lines best effort, and refuse more identity keys (hq ADR 0262 review)
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 delivered
Details
193168e086 
An unplaceable line of a left-out module, such as an access nobody placed, failed the whole machine's
declaration. Say it among what could not be placed instead, never copy the definition's path past a
placement that does not read, and accept a removal only when the decoder is past it.
mesh-admin commented 2026-10-08 16:33:07 +00:00
Author
Contributor
Copy Link
Copy Source

Merge check at 193168e0

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

--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 51 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 0 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

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.039s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	183.028s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.020s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.020s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.015s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.135s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.037s
ok  	github.com/novox/mesh-controller/internal/broker	2.617s
ok  	github.com/novox/mesh-controller/internal/builder	2.080s
ok  	github.com/novox/mesh-controller/internal/catalogue	4.561s
ok  	github.com/novox/mesh-controller/internal/conditions	2.254s
ok  	github.com/novox/mesh-controller/internal/envfile	1.067s
ok  	github.com/novox/mesh-controller/internal/facts	1.069s
ok  	github.com/novox/mesh-controller/internal/identity	4.652s
ok  	github.com/novox/mesh-controller/internal/inventory	84.721s
ok  	github.com/novox/mesh-controller/internal/lease	17.659s
ok  	github.com/novox/mesh-controller/internal/licences	4.276s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.070s
ok  	github.com/novox/mesh-controller/internal/link	47.883s
ok  	github.com/novox/mesh-controller/internal/lint	2.164s
ok  	github.com/novox/mesh-controller/internal/outward	1.096s
ok  	github.com/novox/mesh-controller/internal/overlay	1.081s
ok  	github.com/novox/mesh-controller/internal/secrets	1.511s
ok  	github.com/novox/mesh-controller/internal/store	3.534s
ok  	github.com/novox/mesh-controller/internal/testbus	1.254s
ok  	github.com/novox/mesh-controller/internal/token	1.023s
**Merge check** at `193168e0` - `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-1791476891336792235` (`builds --log build-1791476891336792235`). ``` --- the gate: build-agent, mesh-controller, route-proxy mesh-controller: ok, 51 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 0 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 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.039s ok github.com/novox/mesh-controller/cmd/mesh-controller 183.028s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.020s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.020s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.015s ok github.com/novox/mesh-controller/examples/route-proxy 1.135s ok github.com/novox/mesh-controller/internal/artifacts 1.037s ok github.com/novox/mesh-controller/internal/broker 2.617s ok github.com/novox/mesh-controller/internal/builder 2.080s ok github.com/novox/mesh-controller/internal/catalogue 4.561s ok github.com/novox/mesh-controller/internal/conditions 2.254s ok github.com/novox/mesh-controller/internal/envfile 1.067s ok github.com/novox/mesh-controller/internal/facts 1.069s ok github.com/novox/mesh-controller/internal/identity 4.652s ok github.com/novox/mesh-controller/internal/inventory 84.721s ok github.com/novox/mesh-controller/internal/lease 17.659s ok github.com/novox/mesh-controller/internal/licences 4.276s ok github.com/novox/mesh-controller/internal/licences/adapters 1.070s ok github.com/novox/mesh-controller/internal/link 47.883s ok github.com/novox/mesh-controller/internal/lint 2.164s ok github.com/novox/mesh-controller/internal/outward 1.096s ok github.com/novox/mesh-controller/internal/overlay 1.081s ok github.com/novox/mesh-controller/internal/secrets 1.511s ok github.com/novox/mesh-controller/internal/store 3.534s ok github.com/novox/mesh-controller/internal/testbus 1.254s ok github.com/novox/mesh-controller/internal/token 1.023s ```
mesh-admin merged commit 7f65e62743 into main 2026-10-08 16:37:43 +00:00
mesh-admin deleted branch feat/left-out-keeps-what-it-provides 2026-10-08 16:37:43 +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#162