Say a module assigned and left out of its machine's declaration as a condition (issue 380) #223

Merged
mesh-admin merged 4 commits from fix/380-a-left-out-module-is-said into main 2026-10-11 17:36:58 +00:00
Contributor

Fixes novox/hq issue 380 (a module assigned to a node but left out of every push for days raises no condition), as decided in its note 5.

What changes

  • The self-check's D1 also judges left-out modules (cmd/mesh-controller/left_out.go, called from probeDeclarations in probes.go, from the resolution D1 already makes, so no extra resolution per machine). Every 5 minutes, each machine's set is judged as its next send would judge it (Resolution.LeftOutBecause, the send's own judgement, nothing allocated), and one condition is raised per module left out, on that machine, key module.<module>.<machine>.left-out:
    • cause is a ${setting:…} nobody set (new typed catalogue.UnsetSettingError, same words as before): kind needs-operator; the summary names the module, the setting and the command (settings set <module> '{"<key>": …}' --node <machine>);
    • any other cause: kind left-out, a warning, with the reason as evidence (kept out of the summary so the operator's channel does not withhold it).
    • Always a warning, resolved by the operator, never escalated by age (as ADR 0283 decision 5). Cleared by D1's Reconcile on the first run that no longer finds it: composed again, or unassigned.
    • A module left out because its stored manifest has an unknown key is not raised per machine: the catalogue's unknown-field condition already says it for the whole mesh (ADR 0262). It is still listed in status and node, and status says that those raise none of their own.
  • The health judge leaves it alone: judgeModuleHealth cleared every standing needs-operator on a machine that a statement did not repeat. It now skips conditions with the left-out token; a wait's own needs-operator still clears as before (tested).
  • status gains "N module(s) assigned, not applied" with the same reason, not-applied in --json (with unread-manifest where no condition is raised), and is not called well while there is one. node show lists them under "assigned, not applied", and says so when it cannot tell.
  • An omission stays a finding: the send is unchanged.
  • Operator-read words follow the hq glossary: manifest, declaration, send.

What the operator sees on rollout

Read-only check at 04:40 on 2026-10-11 (mesh-controller.plan with diff for ace, g14, novox and shanks; the diff prints every left-out module first): no module is left out on any of the four machines today, so rollout raises no condition. nfs-server on ace, the issue's case, now composes: node ace shows nfs-server.exports and nfs-server.server healthy. The status line and the conditions appear only when a module is next left out.

Tests (store-free)

left_out_test.go uses the real shape: the nfs-server manifest at mesh-catalog 48fba44, which says ${setting:shares} and gives the exact reason the live push printed.

  • a setting nobody gave raises needs-operator naming the module, the setting and the command; plain words checked
  • another cause (a setting with a line break) raises a left-out warning with the reason as evidence
  • raised; a health statement does not clear it; still a warning after 72 h; clears when the setting is given; raised again; clears when unassigned
  • a wait's needs-operator on the same machine still clears when its statement stops naming it, while the left-out one stays
  • D1 raises both kinds; status, status --json and node lines list it

On main the tests do not compile (the functions do not exist). With the health-judge guard removed, the clearing test fails (a health statement that says nothing of the module cleared its left-out condition).

go vet ./... and go test ./cmd/mesh-controller/ ./internal/catalogue/ -count=1 pass. Touches no file of #220 or #222. standing_test.go only follows showNode's new signature.

Related: issue 231 (mesh-controller #211), ADR 0283, ADR 0292.

Fixes novox/hq issue 380 (a module assigned to a node but left out of every push for days raises no condition), as decided in its note 5. ## What changes - **The self-check's D1 also judges left-out modules** (`cmd/mesh-controller/left_out.go`, called from `probeDeclarations` in `probes.go`, from the resolution D1 already makes, so no extra resolution per machine). Every 5 minutes, each machine's set is judged as its next send would judge it (`Resolution.LeftOutBecause`, the send's own judgement, nothing allocated), and one condition is raised per module left out, on that machine, key `module.<module>.<machine>.left-out`: - cause is a `${setting:…}` nobody set (new typed `catalogue.UnsetSettingError`, same words as before): kind **needs-operator**; the summary names the module, the setting and the command (`settings set <module> '{"<key>": …}' --node <machine>`); - any other cause: kind **left-out**, a warning, with the reason as evidence (kept out of the summary so the operator's channel does not withhold it). - Always a warning, resolved by the operator, never escalated by age (as ADR 0283 decision 5). Cleared by D1's `Reconcile` on the first run that no longer finds it: composed again, or unassigned. - A module left out because its stored manifest has an unknown key is not raised per machine: the catalogue's `unknown-field` condition already says it for the whole mesh (ADR 0262). It is still listed in status and node, and status says that those raise none of their own. - **The health judge leaves it alone**: `judgeModuleHealth` cleared every standing needs-operator on a machine that a statement did not repeat. It now skips conditions with the `left-out` token; a wait's own needs-operator still clears as before (tested). - **`status`** gains "N module(s) assigned, not applied" with the same reason, `not-applied` in `--json` (with `unread-manifest` where no condition is raised), and is not called well while there is one. **`node show`** lists them under "assigned, not applied", and says so when it cannot tell. - An omission stays a finding: the send is unchanged. - Operator-read words follow the hq glossary: manifest, declaration, send. ## What the operator sees on rollout Read-only check at 04:40 on 2026-10-11 (`mesh-controller.plan` with diff for ace, g14, novox and shanks; the diff prints every left-out module first): **no module is left out on any of the four machines today**, so rollout raises no condition. nfs-server on ace, the issue's case, now composes: `node ace` shows nfs-server.exports and nfs-server.server healthy. The status line and the conditions appear only when a module is next left out. ## Tests (store-free) `left_out_test.go` uses the real shape: the nfs-server manifest at mesh-catalog 48fba44, which says `${setting:shares}` and gives the exact reason the live push printed. - a setting nobody gave raises needs-operator naming the module, the setting and the command; plain words checked - another cause (a setting with a line break) raises a left-out warning with the reason as evidence - raised; a health statement does not clear it; still a warning after 72 h; clears when the setting is given; raised again; clears when unassigned - a wait's needs-operator on the same machine still clears when its statement stops naming it, while the left-out one stays - D1 raises both kinds; status, status --json and node lines list it On main the tests do not compile (the functions do not exist). With the health-judge guard removed, the clearing test fails (`a health statement that says nothing of the module cleared its left-out condition`). `go vet ./...` and `go test ./cmd/mesh-controller/ ./internal/catalogue/ -count=1` pass. Touches no file of #220 or #222. `standing_test.go` only follows `showNode`'s new signature. Related: issue 231 (mesh-controller #211), ADR 0283, ADR 0292.
mesh-admin added 1 commit 2026-10-11 02:44:16 +00:00
Say a module assigned and left out of its machine's composition as a condition (issue 380)
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…
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery superseded: a newer head of the same pull request
a330c564ba
A push leaves out a module whose settings do not compose and sends the rest,
which is right, but only plan said so: nfs-server ran nowhere for days while
the operator believed it ran. The self-check now raises needs-operator for a
setting nobody gave, naming the setting and the command, and left-out for any
other cause; both warnings, cleared once the module composes or is unassigned.
status and node show list the same modules as assigned, not applied.
Author
Contributor

Delivery novox/mesh-controller@c385ed2a1766 — delivered since 2026-10-11T17:48:16Z

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

  • tier 0: mesh-controller
  • tier 1: build-agent
  • ace: receives build-agent
  • g14: receives build-agent
  • novox: receives mesh-controller, build-agent
  • shanks: receives build-agent
  • build-agent keeps data (ADR 0233): what it holds is backed up before it moves

Machines

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

Transitions

  • 2026-10-11 17:28 (new) → proposed (announced): novox/mesh-controller#223's head announced
  • 2026-10-11 17:36 proposed → checked (checked): the verdict names this commit
  • 2026-10-11 17:36 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-11 17:38 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-11 17:38 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 — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
  • 2026-10-11 17:48 delivering → delivered (done): its walk is done, carrying its own commit: 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@c385ed2a1766` — **delivered** since 2026-10-11T17:48:16Z **Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller - tier 1: build-agent - ace: receives build-agent - g14: receives build-agent - novox: receives mesh-controller, build-agent - shanks: receives build-agent - build-agent keeps data (ADR 0233): what it holds is backed up before it moves **Machines** - mesh-controller on novox: passed — healthy 3 times over 3m40s - mesh-controller on the rest running it: sent - build-agent on ace: passed — healthy 3 times over 3m24s - build-agent on the rest running it: sent **Transitions** - 2026-10-11 17:28 (new) → proposed (announced): novox/mesh-controller#223's head announced - 2026-10-11 17:36 proposed → checked (checked): the verdict names this commit - 2026-10-11 17:36 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-11 17:38 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-11 17:38 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 — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-11 17:48 delivering → delivered (done): its walk is done, carrying its own commit: 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`.
Author
Contributor

Merge check at a330c564

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

--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 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-11T02:40:01Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T02:40:01Z

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.037s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	216.786s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.020s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.026s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.017s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.147s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.119s
?   	github.com/novox/mesh-controller/internal/beside	[no test files]
ok  	github.com/novox/mesh-controller/internal/broker	2.699s
ok  	github.com/novox/mesh-controller/internal/builder	4.928s
ok  	github.com/novox/mesh-controller/internal/catalogue	7.348s
ok  	github.com/novox/mesh-controller/internal/conditions	2.541s
ok  	github.com/novox/mesh-controller/internal/envfile	1.085s
ok  	github.com/novox/mesh-controller/internal/facts	1.091s
ok  	github.com/novox/mesh-controller/internal/identity	5.007s
ok  	github.com/novox/mesh-controller/internal/inventory	82.615s
ok  	github.com/novox/mesh-controller/internal/lease	17.752s
ok  	github.com/novox/mesh-controller/internal/licences	4.660s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.080s
ok  	github.com/novox/mesh-controller/internal/link	61.015s
ok  	github.com/novox/mesh-controller/internal/lint	2.718s
ok  	github.com/novox/mesh-controller/internal/outward	1.118s
ok  	github.com/novox/mesh-controller/internal/overlay	1.035s
ok  	github.com/novox/mesh-controller/internal/secrets	1.433s
ok  	github.com/novox/mesh-controller/internal/store	3.937s
ok  	github.com/novox/mesh-controller/internal/testbus	1.272s
ok  	github.com/novox/mesh-controller/internal/token	1.019s
**Merge check** at `a330c564` - `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-1791686684353916903` (`builds --log build-1791686684353916903`). ``` --- the gate: build-agent, mesh-controller, route-proxy mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8) long-running resources without health: 1 files asking for a setting without saying whether it is trusted: 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-11T02:40:01Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-11T02:40:01Z 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.037s ok github.com/novox/mesh-controller/cmd/mesh-controller 216.786s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.020s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.026s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.017s ok github.com/novox/mesh-controller/examples/route-proxy 1.147s ok github.com/novox/mesh-controller/internal/artifacts 1.119s ? github.com/novox/mesh-controller/internal/beside [no test files] ok github.com/novox/mesh-controller/internal/broker 2.699s ok github.com/novox/mesh-controller/internal/builder 4.928s ok github.com/novox/mesh-controller/internal/catalogue 7.348s ok github.com/novox/mesh-controller/internal/conditions 2.541s ok github.com/novox/mesh-controller/internal/envfile 1.085s ok github.com/novox/mesh-controller/internal/facts 1.091s ok github.com/novox/mesh-controller/internal/identity 5.007s ok github.com/novox/mesh-controller/internal/inventory 82.615s ok github.com/novox/mesh-controller/internal/lease 17.752s ok github.com/novox/mesh-controller/internal/licences 4.660s ok github.com/novox/mesh-controller/internal/licences/adapters 1.080s ok github.com/novox/mesh-controller/internal/link 61.015s ok github.com/novox/mesh-controller/internal/lint 2.718s ok github.com/novox/mesh-controller/internal/outward 1.118s ok github.com/novox/mesh-controller/internal/overlay 1.035s ok github.com/novox/mesh-controller/internal/secrets 1.433s ok github.com/novox/mesh-controller/internal/store 3.937s ok github.com/novox/mesh-controller/internal/testbus 1.272s ok github.com/novox/mesh-controller/internal/token 1.019s ```
jschoubben added 1 commit 2026-10-11 09:10:32 +00:00
Use the glossary's words, say which modules raise a condition, and judge left-out modules in D1 (review of #223)
mesh/delivery superseded: a newer head of the same pull request
mesh/merge-gate pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without …
mesh/repo-check pass: its merge-check.sh passed
419d662ad8
The operator reads manifest, declaration and send, not definition,
composition and update. D1 already resolves every machine, so the
left-out judgement rides on it instead of resolving each machine again.
A test holds that a wait's own needs-operator still clears beside it.
mesh-admin changed title from Say a module assigned and left out of its machine's composition as a condition (issue 380) to Say a module assigned and left out of its machine's declaration as a condition (issue 380) 2026-10-11 09:14:14 +00:00
jschoubben added 1 commit 2026-10-11 09:14:15 +00:00
Restore the tracked controller binary a local build overwrote, and hold that D1 never clears a wait (review of #223)
mesh/merge-gate pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without …
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery superseded: a newer head of the same pull request
c14fe2776c
The binary in 419d662 came from a build into the worktree, not from the
change. node show says send, as the glossary does. A test now reconciles D1
beside a wait's needs-operator, which a wait raised under D1's source would fail.
Author
Contributor

Merge check at 419d662a

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

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

  • tier 0: mesh-controller
  • tier 1: build-agent
  • ace: receives build-agent
  • g14: receives build-agent
  • novox: receives mesh-controller, build-agent
  • shanks: receives build-agent
  • build-agent keeps data (ADR 0233): what it holds is backed up before it moves

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

--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 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-11T09:10:50Z 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-11T09:10:50Z

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 2 module(s) in 2 tier(s): build-agent, mesh-controller
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-controller/cmd/mesh-builder	1.042s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	269.386s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.022s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.034s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.024s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.126s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.079s
?   	github.com/novox/mesh-controller/internal/beside	[no test files]
ok  	github.com/novox/mesh-controller/internal/broker	2.980s
ok  	github.com/novox/mesh-controller/internal/builder	3.326s
ok  	github.com/novox/mesh-controller/internal/catalogue	7.738s
ok  	github.com/novox/mesh-controller/internal/conditions	2.681s
ok  	github.com/novox/mesh-controller/internal/envfile	1.027s
ok  	github.com/novox/mesh-controller/internal/facts	1.025s
ok  	github.com/novox/mesh-controller/internal/identity	12.021s
ok  	github.com/novox/mesh-controller/internal/inventory	107.173s
ok  	github.com/novox/mesh-controller/internal/lease	17.973s
ok  	github.com/novox/mesh-controller/internal/licences	11.235s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.011s
ok  	github.com/novox/mesh-controller/internal/link	65.330s
ok  	github.com/novox/mesh-controller/internal/lint	2.442s
ok  	github.com/novox/mesh-controller/internal/outward	1.037s
ok  	github.com/novox/mesh-controller/internal/overlay	1.023s
ok  	github.com/novox/mesh-controller/internal/secrets	1.422s
ok  	github.com/novox/mesh-controller/internal/store	8.567s
ok  	github.com/novox/mesh-controller/internal/testbus	1.367s
ok  	github.com/novox/mesh-controller/internal/token	1.014s
**Merge check** at `419d662a` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller - tier 1: build-agent - ace: receives build-agent - g14: receives build-agent - novox: receives mesh-controller, build-agent - shanks: receives build-agent - build-agent keeps data (ADR 0233): what it holds is backed up before it moves Run by the build seat on novox as `build-1791709854650616115` (`builds --log build-1791709854650616115`). ``` --- the gate: build-agent, mesh-controller mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8) long-running resources without health: 1 files asking for a setting without saying whether it is trusted: 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-11T09:10:50Z 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-11T09:10:50Z 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 2 module(s) in 2 tier(s): build-agent, mesh-controller --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-controller/cmd/mesh-builder 1.042s ok github.com/novox/mesh-controller/cmd/mesh-controller 269.386s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.022s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.034s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.024s ok github.com/novox/mesh-controller/examples/route-proxy 1.126s ok github.com/novox/mesh-controller/internal/artifacts 1.079s ? github.com/novox/mesh-controller/internal/beside [no test files] ok github.com/novox/mesh-controller/internal/broker 2.980s ok github.com/novox/mesh-controller/internal/builder 3.326s ok github.com/novox/mesh-controller/internal/catalogue 7.738s ok github.com/novox/mesh-controller/internal/conditions 2.681s ok github.com/novox/mesh-controller/internal/envfile 1.027s ok github.com/novox/mesh-controller/internal/facts 1.025s ok github.com/novox/mesh-controller/internal/identity 12.021s ok github.com/novox/mesh-controller/internal/inventory 107.173s ok github.com/novox/mesh-controller/internal/lease 17.973s ok github.com/novox/mesh-controller/internal/licences 11.235s ok github.com/novox/mesh-controller/internal/licences/adapters 1.011s ok github.com/novox/mesh-controller/internal/link 65.330s ok github.com/novox/mesh-controller/internal/lint 2.442s ok github.com/novox/mesh-controller/internal/outward 1.037s ok github.com/novox/mesh-controller/internal/overlay 1.023s ok github.com/novox/mesh-controller/internal/secrets 1.422s ok github.com/novox/mesh-controller/internal/store 8.567s ok github.com/novox/mesh-controller/internal/testbus 1.367s ok github.com/novox/mesh-controller/internal/token 1.014s ```
Author
Contributor

Merge check at c14fe277

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

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

  • tier 0: mesh-controller
  • tier 1: build-agent
  • ace: receives build-agent
  • g14: receives build-agent
  • novox: receives mesh-controller, build-agent
  • shanks: receives build-agent
  • build-agent keeps data (ADR 0233): what it holds is backed up before it moves
  • read by no module's build: cmd/mesh-controller/left_out_test.go, cmd/mesh-controller/standing_test.go, cmd/mesh-controller/testdata/left-out/nfs-server.json

Run by the build seat on g14 as build-1791710069209640941 (builds --log build-1791710069209640941).

--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 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-11T09:12: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-11T09:12: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 2 module(s) in 2 tier(s): build-agent, mesh-controller

notes:
  - cmd/mesh-controller/left_out_test.go, cmd/mesh-controller/standing_test.go and cmd/mesh-controller/testdata/left-out/nfs-server.json read by no module's build, and rebuild nothing (issue 280)
--- 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	227.314s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.008s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.019s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.009s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.150s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.048s
?   	github.com/novox/mesh-controller/internal/beside	[no test files]
ok  	github.com/novox/mesh-controller/internal/broker	2.609s
ok  	github.com/novox/mesh-controller/internal/builder	2.519s
ok  	github.com/novox/mesh-controller/internal/catalogue	6.787s
ok  	github.com/novox/mesh-controller/internal/conditions	2.376s
ok  	github.com/novox/mesh-controller/internal/envfile	1.032s
ok  	github.com/novox/mesh-controller/internal/facts	1.036s
ok  	github.com/novox/mesh-controller/internal/identity	4.079s
ok  	github.com/novox/mesh-controller/internal/inventory	76.736s
ok  	github.com/novox/mesh-controller/internal/lease	17.694s
ok  	github.com/novox/mesh-controller/internal/licences	3.721s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.006s
ok  	github.com/novox/mesh-controller/internal/link	59.195s
ok  	github.com/novox/mesh-controller/internal/lint	2.040s
ok  	github.com/novox/mesh-controller/internal/outward	1.037s
ok  	github.com/novox/mesh-controller/internal/overlay	1.028s
ok  	github.com/novox/mesh-controller/internal/secrets	1.422s
ok  	github.com/novox/mesh-controller/internal/store	3.219s
ok  	github.com/novox/mesh-controller/internal/testbus	1.168s
ok  	github.com/novox/mesh-controller/internal/token	1.012s
**Merge check** at `c14fe277` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller - tier 1: build-agent - ace: receives build-agent - g14: receives build-agent - novox: receives mesh-controller, build-agent - shanks: receives build-agent - build-agent keeps data (ADR 0233): what it holds is backed up before it moves - read by no module's build: cmd/mesh-controller/left_out_test.go, cmd/mesh-controller/standing_test.go, cmd/mesh-controller/testdata/left-out/nfs-server.json Run by the build seat on g14 as `build-1791710069209640941` (`builds --log build-1791710069209640941`). ``` --- the gate: build-agent, mesh-controller mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8) long-running resources without health: 1 files asking for a setting without saying whether it is trusted: 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-11T09:12: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-11T09:12: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 2 module(s) in 2 tier(s): build-agent, mesh-controller notes: - cmd/mesh-controller/left_out_test.go, cmd/mesh-controller/standing_test.go and cmd/mesh-controller/testdata/left-out/nfs-server.json read by no module's build, and rebuild nothing (issue 280) --- 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 227.314s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.008s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.019s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.009s ok github.com/novox/mesh-controller/examples/route-proxy 1.150s ok github.com/novox/mesh-controller/internal/artifacts 1.048s ? github.com/novox/mesh-controller/internal/beside [no test files] ok github.com/novox/mesh-controller/internal/broker 2.609s ok github.com/novox/mesh-controller/internal/builder 2.519s ok github.com/novox/mesh-controller/internal/catalogue 6.787s ok github.com/novox/mesh-controller/internal/conditions 2.376s ok github.com/novox/mesh-controller/internal/envfile 1.032s ok github.com/novox/mesh-controller/internal/facts 1.036s ok github.com/novox/mesh-controller/internal/identity 4.079s ok github.com/novox/mesh-controller/internal/inventory 76.736s ok github.com/novox/mesh-controller/internal/lease 17.694s ok github.com/novox/mesh-controller/internal/licences 3.721s ok github.com/novox/mesh-controller/internal/licences/adapters 1.006s ok github.com/novox/mesh-controller/internal/link 59.195s ok github.com/novox/mesh-controller/internal/lint 2.040s ok github.com/novox/mesh-controller/internal/outward 1.037s ok github.com/novox/mesh-controller/internal/overlay 1.028s ok github.com/novox/mesh-controller/internal/secrets 1.422s ok github.com/novox/mesh-controller/internal/store 3.219s ok github.com/novox/mesh-controller/internal/testbus 1.168s ok github.com/novox/mesh-controller/internal/token 1.012s ```
jschoubben added 1 commit 2026-10-11 17:28:49 +00:00
Merge remote-tracking branch 'origin/main' into fix/380-a-left-out-module-is-said
mesh/merge-gate pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without …
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery delivered
c385ed2a17
Author
Contributor

Merge check at c385ed2a

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

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

  • tier 0: mesh-controller
  • tier 1: build-agent
  • ace: receives build-agent
  • g14: receives build-agent
  • novox: receives mesh-controller, build-agent
  • shanks: receives build-agent
  • build-agent keeps data (ADR 0233): what it holds is backed up before it moves
  • read by no module's build: cmd/mesh-controller/left_out_test.go, cmd/mesh-controller/standing_test.go, cmd/mesh-controller/testdata/left-out/nfs-server.json

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

--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 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-11T17:21:39Z 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-11T17:21:39Z

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.045s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	273.449s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.019s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.024s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.016s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.131s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.061s
?   	github.com/novox/mesh-controller/internal/beside	[no test files]
ok  	github.com/novox/mesh-controller/internal/broker	5.994s
ok  	github.com/novox/mesh-controller/internal/builder	26.843s
ok  	github.com/novox/mesh-controller/internal/catalogue	8.773s
ok  	github.com/novox/mesh-controller/internal/conditions	2.828s
ok  	github.com/novox/mesh-controller/internal/envfile	1.041s
ok  	github.com/novox/mesh-controller/internal/facts	1.039s
ok  	github.com/novox/mesh-controller/internal/identity	8.366s
ok  	github.com/novox/mesh-controller/internal/inventory	111.634s
ok  	github.com/novox/mesh-controller/internal/lease	17.674s
ok  	github.com/novox/mesh-controller/internal/licences	8.099s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.015s
ok  	github.com/novox/mesh-controller/internal/link	64.753s
ok  	github.com/novox/mesh-controller/internal/lint	2.301s
ok  	github.com/novox/mesh-controller/internal/outward	1.047s
ok  	github.com/novox/mesh-controller/internal/overlay	1.030s
ok  	github.com/novox/mesh-controller/internal/secrets	1.471s
ok  	github.com/novox/mesh-controller/internal/store	4.361s
ok  	github.com/novox/mesh-controller/internal/testbus	1.199s
ok  	github.com/novox/mesh-controller/internal/token	1.021s
**Merge check** at `c385ed2a` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller - tier 1: build-agent - ace: receives build-agent - g14: receives build-agent - novox: receives mesh-controller, build-agent - shanks: receives build-agent - build-agent keeps data (ADR 0233): what it holds is backed up before it moves - read by no module's build: cmd/mesh-controller/left_out_test.go, cmd/mesh-controller/standing_test.go, cmd/mesh-controller/testdata/left-out/nfs-server.json Run by the build seat on novox as `build-1791739739513749893` (`builds --log build-1791739739513749893`). ``` --- the gate: build-agent, mesh-controller mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8) long-running resources without health: 1 files asking for a setting without saying whether it is trusted: 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-11T17:21:39Z 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-11T17:21:39Z 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.045s ok github.com/novox/mesh-controller/cmd/mesh-controller 273.449s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.019s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.024s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.016s ok github.com/novox/mesh-controller/examples/route-proxy 1.131s ok github.com/novox/mesh-controller/internal/artifacts 1.061s ? github.com/novox/mesh-controller/internal/beside [no test files] ok github.com/novox/mesh-controller/internal/broker 5.994s ok github.com/novox/mesh-controller/internal/builder 26.843s ok github.com/novox/mesh-controller/internal/catalogue 8.773s ok github.com/novox/mesh-controller/internal/conditions 2.828s ok github.com/novox/mesh-controller/internal/envfile 1.041s ok github.com/novox/mesh-controller/internal/facts 1.039s ok github.com/novox/mesh-controller/internal/identity 8.366s ok github.com/novox/mesh-controller/internal/inventory 111.634s ok github.com/novox/mesh-controller/internal/lease 17.674s ok github.com/novox/mesh-controller/internal/licences 8.099s ok github.com/novox/mesh-controller/internal/licences/adapters 1.015s ok github.com/novox/mesh-controller/internal/link 64.753s ok github.com/novox/mesh-controller/internal/lint 2.301s ok github.com/novox/mesh-controller/internal/outward 1.047s ok github.com/novox/mesh-controller/internal/overlay 1.030s ok github.com/novox/mesh-controller/internal/secrets 1.471s ok github.com/novox/mesh-controller/internal/store 4.361s ok github.com/novox/mesh-controller/internal/testbus 1.199s ok github.com/novox/mesh-controller/internal/token 1.021s ```
mesh-admin merged commit 3b017b228c into main 2026-10-11 17:36:58 +00:00
mesh-admin deleted branch fix/380-a-left-out-module-is-said 2026-10-11 17:36:58 +00:00
This repo is archived. You cannot comment on pull requests.
No Reviewers
2 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-controller#223