A merge that shares nothing with the assembling batch, and whose group waits for no one, is cut at once (hq issue 525, ADR 0304 §1, ADR 0306 §2-3) #250

Merged
mesh-admin merged 4 commits from feat/525-a-lone-merge-skips-the-window into main 2026-10-12 11:46:59 +00:00
Contributor

Why (issue 525 step 3 of 7). ADR 0304 §1 (with ADR 0306 §2-3, both accepted): a merge waits for the merge window only when the assembling batch holds a merge related to it (repository, module including dependents, graph edge, group head) or its delivery group has a member still to merge. Today every merge waits the window (up to 90 s rolling, 10 min at most), unrelated or not. Walks stay one at a time in this step; cutting at once means the batch's window is closed at once.

What changes

  • batches.go: theOpenBatch → batchToJoin: a merge joins an assembling batch of its kind it is related to (related.go, #242); related to two or more, the newer are folded into the oldest in one SavePlansMoving; related to none and in no waiting group, a new batch with PlanBatch.CutAtOnce (JSON in the plan's delivery, no migration). relatedBatches/footprintAsCut relate against what the cut would move: the waiting walks a cut folds in, and each batch's moves recomputed against the catalogue as it reads now, so a batch is never under-related; a merge kept with no moves is related to everything.
  • group_wait.go: when a headed merge is heard, the controller asks mesh-delivery.groups (bounded 3 s, before the plans are held): it waits only when another repository's member of its group has an open pull request whose merge the controller does not already hold. No head, no group, or every other member merged/closed: no wait. Any failure to get an answer waits (the safe side), and the batch's words say why (PlanBatch.Waits).
  • delivery.go batchToWalkAgain (ADR 0299 stop): re-walks the stopped walk's other merges in a related batch or a new one, not "the open batch of its kind".
  • batches_watch.go: S18/S19 treat a cut-at-once window as closed when the batch was made. keepBatch keeps the flag; a merge joining clears it.
  • internal/broker: the controller's grant gains mesh.seat.mesh-delivery.tool.groups (golden updated); testdata/beside/mesh-host recaptured at mesh-host a76baa4b (#85, the installer's user list carries it).

Tests (make check, all 26 packages ok): lone_merge_test.go — a lone merge sharing nothing is cut at once; related merges (same repository, a dependent, a graph edge, the same group head) join and wait; a group with an open member waits even alone and its sibling joins; a lookup failure waits with its reason; merged/closed members make nobody wait; a merge related to two batches folds them; with a walk open a cut-at-once batch queues behind it; a stop's other merges walk in their own batch; carry relates a lone merge to a waiting walk the cut would fold (fails with the carry disabled). Existing window tests keep their premise through named group-lookup stubs (noGroups, groupsWaiting, everyHeadWaits); no assertion weakened.

Core: the controller. One delivery of the controller at a time.

**Why** (issue 525 step 3 of 7). ADR 0304 §1 (with ADR 0306 §2-3, both accepted): a merge waits for the merge window only when the assembling batch holds a merge related to it (repository, module including dependents, graph edge, group head) or its delivery group has a member still to merge. Today every merge waits the window (up to 90 s rolling, 10 min at most), unrelated or not. Walks stay one at a time in this step; cutting at once means the batch's window is closed at once. **What changes** - `batches.go`: `theOpenBatch` → `batchToJoin`: a merge joins an assembling batch of its kind it is related to (`related.go`, #242); related to two or more, the newer are folded into the oldest in one `SavePlansMoving`; related to none and in no waiting group, a new batch with `PlanBatch.CutAtOnce` (JSON in the plan's delivery, no migration). `relatedBatches`/`footprintAsCut` relate against what the cut would move: the waiting walks a cut folds in, and each batch's moves recomputed against the catalogue as it reads now, so a batch is never under-related; a merge kept with no moves is related to everything. - `group_wait.go`: when a headed merge is heard, the controller asks `mesh-delivery.groups` (bounded 3 s, before the plans are held): it waits only when another repository's member of its group has an open pull request whose merge the controller does not already hold. No head, no group, or every other member merged/closed: no wait. **Any failure to get an answer waits** (the safe side), and the batch's words say why (`PlanBatch.Waits`). - `delivery.go` `batchToWalkAgain` (ADR 0299 stop): re-walks the stopped walk's other merges in a related batch or a new one, not "the open batch of its kind". - `batches_watch.go`: S18/S19 treat a cut-at-once window as closed when the batch was made. `keepBatch` keeps the flag; a merge joining clears it. - `internal/broker`: the controller's grant gains `mesh.seat.mesh-delivery.tool.groups` (golden updated); `testdata/beside/mesh-host` recaptured at mesh-host a76baa4b (#85, the installer's user list carries it). **Tests** (`make check`, all 26 packages ok): `lone_merge_test.go` — a lone merge sharing nothing is cut at once; related merges (same repository, a dependent, a graph edge, the same group head) join and wait; a group with an open member waits even alone and its sibling joins; a lookup failure waits with its reason; merged/closed members make nobody wait; a merge related to two batches folds them; with a walk open a cut-at-once batch queues behind it; a stop's other merges walk in their own batch; carry relates a lone merge to a waiting walk the cut would fold (fails with the carry disabled). Existing window tests keep their premise through named group-lookup stubs (`noGroups`, `groupsWaiting`, `everyHeadWaits`); no assertion weakened. **Core**: the controller. One delivery of the controller at a time.
mesh-admin added 3 commits 2026-10-12 10:32:23 +00:00
A merge waited the whole window even when nothing assembling shared anything
with it. It now joins only a batch it is related to (ADR 0304 §1, read by ADR
0306 §3: repository, a module the cut would move, a graph edge, a group head),
folding the newer into the oldest when it relates to two. A merge related to
none starts a batch whose window is closed at once (PlanBatch.CutAtOnce),
unless its delivery group may still have a member to merge (ADR 0306 §2).

The controller cannot see a group's unmerged members (that is mesh-delivery's
record), so a merge from any head still waits, in a batch of its own: the safe
error is to wait. Walks stay one at a time; a batch cut at once queues behind
an open walk. A stop's merges walked again join a related batch, or their own.
A merge from any head waited for the window because the controller could not
see a group's members, so the window skip changed nothing in production and
unrelated merges walked one after another. The controller now asks
mesh-delivery's groups, within 3 s and before the plans are held: a merge
waits only when its head's group has another member whose pull request is
open and whose merge it does not keep yet (ADR 0306 §2). No answer means it
waits, and its batch says why. A headed merge in no waiting group and related
to no batch is cut at once, as one from no head is (ADR 0304 §1, ADR 0306 §3).

The controller's grant names mesh-delivery.groups. The installer's first user
list in mesh-host must carry it too before the genesis test can pass.
Judge the installer's user list against mesh-host with the groups grant (hq issue 525)
mesh/repo-check fail: its merge-check.sh failed: --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.78s)
mesh/delivery superseded: a newer head of the same pull request
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…
6e5a1df575
The controller now asks mesh-delivery.groups, and mesh-host a76baa4b carries
that grant in the installer's first user list (mesh-host #85). The captured
copy is moved to that commit so the genesis test judges the list that ships.
Author
Contributor

Delivery novox/mesh-controller@71b3aeaf2c74 — delivered since 2026-10-12T12:02:37Z

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
  • grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine

Machines

  • mesh-controller on novox: passed — healthy 3 times over 4m8s
  • mesh-controller on the rest running it: sent
  • build-agent on ace: passed — healthy 1 times over 1m39s
  • build-agent on the rest running it: sent
  • route-proxy on ace: passed — healthy 1 times over 1m25s
  • route-proxy on the rest running it: sent

Transitions

  • 2026-10-12 10:54 (new) → proposed (announced): novox/mesh-controller#250's head announced
  • 2026-10-12 11:01 proposed → checked (checked): the verdict names this commit
  • 2026-10-12 11:01 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
  • 2026-10-12 11:32 rejected → proposed (recheck): its repo-check read mesh-host at the commit the mesh ran, which lacked #85's groups grant; mesh-host #86 is now delivered and carries it
  • 2026-10-12 11:41 proposed → checked (checked): the verdict names this commit
  • 2026-10-12 11:41 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-12 11:50 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-12 11:50 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-12 12:02 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@71b3aeaf2c74` — **delivered** since 2026-10-12T12:02:37Z **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 - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine **Machines** - mesh-controller on novox: passed — healthy 3 times over 4m8s - mesh-controller on the rest running it: sent - build-agent on ace: passed — healthy 1 times over 1m39s - build-agent on the rest running it: sent - route-proxy on ace: passed — healthy 1 times over 1m25s - route-proxy on the rest running it: sent **Transitions** - 2026-10-12 10:54 (new) → proposed (announced): novox/mesh-controller#250's head announced - 2026-10-12 11:01 proposed → checked (checked): the verdict names this commit - 2026-10-12 11:01 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed - 2026-10-12 11:32 rejected → proposed (recheck): its repo-check read mesh-host at the commit the mesh ran, which lacked #85's groups grant; mesh-host #86 is now delivered and carries it - 2026-10-12 11:41 proposed → checked (checked): the verdict names this commit - 2026-10-12 11:41 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-12 11:50 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-12 11:50 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-12 12:02 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 6e5a1df5

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

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
  • grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine

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

--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 57 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-12T10:31:44Z 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-12T10:31:44Z

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.041s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	285.979s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.033s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.059s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.023s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.229s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.092s
?   	github.com/novox/mesh-controller/internal/beside	[no test files]
--- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.78s)
    genesis_template_test.go:29: judged against /var/lib/build-agent/workspace/check/mesh-host as cloned beside this check
    genesis_template_test.go:39: the installer's user list does not let the controller publish [mesh.seat.mesh-delivery.tool.groups] — it would come up and be refused on the first thing it tried
FAIL
FAIL	github.com/novox/mesh-controller/internal/broker	3.453s
ok  	github.com/novox/mesh-controller/internal/builder	19.160s
ok  	github.com/novox/mesh-controller/internal/catalogue	7.882s
ok  	github.com/novox/mesh-controller/internal/conditions	2.639s
ok  	github.com/novox/mesh-controller/internal/envfile	1.075s
ok  	github.com/novox/mesh-controller/internal/facts	1.068s
ok  	github.com/novox/mesh-controller/internal/identity	4.977s
ok  	github.com/novox/mesh-controller/internal/inventory	104.799s
ok  	github.com/novox/mesh-controller/internal/lease	17.767s
ok  	github.com/novox/mesh-controller/internal/licences	4.571s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.063s
ok  	github.com/novox/mesh-controller/internal/link	63.015s
ok  	github.com/novox/mesh-controller/internal/lint	2.470s
ok  	github.com/novox/mesh-controller/internal/outward	1.085s
ok  	github.com/novox/mesh-controller/internal/overlay	1.085s
ok  	github.com/novox/mesh-controller/internal/secrets	1.526s
ok  	github.com/novox/mesh-controller/internal/store	3.523s
ok  	github.com/novox/mesh-controller/internal/testbus	1.261s
ok  	github.com/novox/mesh-controller/internal/token	1.015s
FAIL
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.78s)
    genesis_template_test.go:29: judged against /var/lib/build-agent/workspace/check/mesh-host as cloned beside this check
    genesis_template_test.go:39: the installer's user list does not let the controller publish [mesh.seat.mesh-delivery.tool.groups] — it would come up and be refused on the first thing it tried
FAIL	github.com/novox/mesh-controller/internal/broker	3.453s
**Merge check** at `6e5a1df5` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy) - `mesh/repo-check`: **FAIL** — its merge-check.sh failed: --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.78s) **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 - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine Run by the build seat on shanks as `build-1791801156598410912` (`builds --log build-1791801156598410912`). ``` --- the gate: build-agent, mesh-controller, route-proxy mesh-controller: ok, 57 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-12T10:31:44Z 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-12T10:31:44Z 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.041s ok github.com/novox/mesh-controller/cmd/mesh-controller 285.979s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.033s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.059s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.023s ok github.com/novox/mesh-controller/examples/route-proxy 1.229s ok github.com/novox/mesh-controller/internal/artifacts 1.092s ? github.com/novox/mesh-controller/internal/beside [no test files] --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.78s) genesis_template_test.go:29: judged against /var/lib/build-agent/workspace/check/mesh-host as cloned beside this check genesis_template_test.go:39: the installer's user list does not let the controller publish [mesh.seat.mesh-delivery.tool.groups] — it would come up and be refused on the first thing it tried FAIL FAIL github.com/novox/mesh-controller/internal/broker 3.453s ok github.com/novox/mesh-controller/internal/builder 19.160s ok github.com/novox/mesh-controller/internal/catalogue 7.882s ok github.com/novox/mesh-controller/internal/conditions 2.639s ok github.com/novox/mesh-controller/internal/envfile 1.075s ok github.com/novox/mesh-controller/internal/facts 1.068s ok github.com/novox/mesh-controller/internal/identity 4.977s ok github.com/novox/mesh-controller/internal/inventory 104.799s ok github.com/novox/mesh-controller/internal/lease 17.767s ok github.com/novox/mesh-controller/internal/licences 4.571s ok github.com/novox/mesh-controller/internal/licences/adapters 1.063s ok github.com/novox/mesh-controller/internal/link 63.015s ok github.com/novox/mesh-controller/internal/lint 2.470s ok github.com/novox/mesh-controller/internal/outward 1.085s ok github.com/novox/mesh-controller/internal/overlay 1.085s ok github.com/novox/mesh-controller/internal/secrets 1.526s ok github.com/novox/mesh-controller/internal/store 3.523s ok github.com/novox/mesh-controller/internal/testbus 1.261s ok github.com/novox/mesh-controller/internal/token 1.015s FAIL --- what failed, picked from the whole of its output (the whole is in the build's log) --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.78s) genesis_template_test.go:29: judged against /var/lib/build-agent/workspace/check/mesh-host as cloned beside this check genesis_template_test.go:39: the installer's user list does not let the controller publish [mesh.seat.mesh-delivery.tool.groups] — it would come up and be refused on the first thing it tried FAIL github.com/novox/mesh-controller/internal/broker 3.453s ```
jschoubben added 1 commit 2026-10-12 10:54:14 +00:00
Keep a group member of the other kind's batch from being overtaken (hq issue 525)
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 delivered
71b3aeaf2c
A merge's group member counted as merged when its merge waited in any batch,
but kinds never share a batch: the later member got a batch of its own, cut
at once, and walked before the earlier member's batch was cut, breaking the
group's order (ADR 0276 §5). Only a member kept in a batch of the merge's own
kind counts as merged now; one kept in the other kind's keeps the merge
waiting, and its batch names that member, so the two are cut in the order
their windows close (review of #250).
Author
Contributor

Merge check at 71b3aeaf

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

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
  • grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine
  • read by no module's build: cmd/mesh-controller/batches_test.go, cmd/mesh-controller/issue459_test.go, cmd/mesh-controller/lone_merge_test.go, internal/broker/testdata/composed.conf, testdata/beside/CAPTURED, testdata/beside/mesh-host/examples/foundation-first-node-nats.lock, testdata/beside/mesh-host/internal/apply/placement_guard.go.captured

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

--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 57 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-12T10:50:44Z 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-12T10:50:44Z

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

notes:
  - cmd/mesh-controller/batches_test.go, cmd/mesh-controller/issue459_test.go, cmd/mesh-controller/lone_merge_test.go, internal/broker/testdata/composed.conf, testdata/beside/CAPTURED, testdata/beside/mesh-host/examples/foundation-first-node-nats.lock and testdata/beside/mesh-host/internal/apply/placement_guard.go.captured 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.046s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	260.971s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.046s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.074s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.051s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.223s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.110s
?   	github.com/novox/mesh-controller/internal/beside	[no test files]
--- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.79s)
    genesis_template_test.go:29: judged against /var/lib/build-agent/workspace/check/mesh-host as cloned beside this check
    genesis_template_test.go:39: the installer's user list does not let the controller publish [mesh.seat.mesh-delivery.tool.groups] — it would come up and be refused on the first thing it tried
FAIL
FAIL	github.com/novox/mesh-controller/internal/broker	3.557s
ok  	github.com/novox/mesh-controller/internal/builder	19.122s
ok  	github.com/novox/mesh-controller/internal/catalogue	7.995s
ok  	github.com/novox/mesh-controller/internal/conditions	2.619s
ok  	github.com/novox/mesh-controller/internal/envfile	1.062s
ok  	github.com/novox/mesh-controller/internal/facts	1.057s
ok  	github.com/novox/mesh-controller/internal/identity	5.271s
ok  	github.com/novox/mesh-controller/internal/inventory	101.019s
ok  	github.com/novox/mesh-controller/internal/lease	17.719s
ok  	github.com/novox/mesh-controller/internal/licences	4.586s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.055s
ok  	github.com/novox/mesh-controller/internal/link	61.983s
ok  	github.com/novox/mesh-controller/internal/lint	2.462s
ok  	github.com/novox/mesh-controller/internal/outward	1.086s
ok  	github.com/novox/mesh-controller/internal/overlay	1.063s
ok  	github.com/novox/mesh-controller/internal/secrets	1.559s
ok  	github.com/novox/mesh-controller/internal/store	3.541s
ok  	github.com/novox/mesh-controller/internal/testbus	1.262s
ok  	github.com/novox/mesh-controller/internal/token	1.015s
FAIL
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.79s)
    genesis_template_test.go:29: judged against /var/lib/build-agent/workspace/check/mesh-host as cloned beside this check
    genesis_template_test.go:39: the installer's user list does not let the controller publish [mesh.seat.mesh-delivery.tool.groups] — it would come up and be refused on the first thing it tried
FAIL	github.com/novox/mesh-controller/internal/broker	3.557s
**Merge check** at `71b3aeaf` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy) - `mesh/repo-check`: **FAIL** — its merge-check.sh failed: --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.79s) **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 - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine - read by no module's build: cmd/mesh-controller/batches_test.go, cmd/mesh-controller/issue459_test.go, cmd/mesh-controller/lone_merge_test.go, internal/broker/testdata/composed.conf, testdata/beside/CAPTURED, testdata/beside/mesh-host/examples/foundation-first-node-nats.lock, testdata/beside/mesh-host/internal/apply/placement_guard.go.captured Run by the build seat on shanks as `build-1791802477581465111` (`builds --log build-1791802477581465111`). ``` --- the gate: build-agent, mesh-controller, route-proxy mesh-controller: ok, 57 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-12T10:50:44Z 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-12T10:50:44Z 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 notes: - cmd/mesh-controller/batches_test.go, cmd/mesh-controller/issue459_test.go, cmd/mesh-controller/lone_merge_test.go, internal/broker/testdata/composed.conf, testdata/beside/CAPTURED, testdata/beside/mesh-host/examples/foundation-first-node-nats.lock and testdata/beside/mesh-host/internal/apply/placement_guard.go.captured 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.046s ok github.com/novox/mesh-controller/cmd/mesh-controller 260.971s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.046s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.074s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.051s ok github.com/novox/mesh-controller/examples/route-proxy 1.223s ok github.com/novox/mesh-controller/internal/artifacts 1.110s ? github.com/novox/mesh-controller/internal/beside [no test files] --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.79s) genesis_template_test.go:29: judged against /var/lib/build-agent/workspace/check/mesh-host as cloned beside this check genesis_template_test.go:39: the installer's user list does not let the controller publish [mesh.seat.mesh-delivery.tool.groups] — it would come up and be refused on the first thing it tried FAIL FAIL github.com/novox/mesh-controller/internal/broker 3.557s ok github.com/novox/mesh-controller/internal/builder 19.122s ok github.com/novox/mesh-controller/internal/catalogue 7.995s ok github.com/novox/mesh-controller/internal/conditions 2.619s ok github.com/novox/mesh-controller/internal/envfile 1.062s ok github.com/novox/mesh-controller/internal/facts 1.057s ok github.com/novox/mesh-controller/internal/identity 5.271s ok github.com/novox/mesh-controller/internal/inventory 101.019s ok github.com/novox/mesh-controller/internal/lease 17.719s ok github.com/novox/mesh-controller/internal/licences 4.586s ok github.com/novox/mesh-controller/internal/licences/adapters 1.055s ok github.com/novox/mesh-controller/internal/link 61.983s ok github.com/novox/mesh-controller/internal/lint 2.462s ok github.com/novox/mesh-controller/internal/outward 1.086s ok github.com/novox/mesh-controller/internal/overlay 1.063s ok github.com/novox/mesh-controller/internal/secrets 1.559s ok github.com/novox/mesh-controller/internal/store 3.541s ok github.com/novox/mesh-controller/internal/testbus 1.262s ok github.com/novox/mesh-controller/internal/token 1.015s FAIL --- what failed, picked from the whole of its output (the whole is in the build's log) --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.79s) genesis_template_test.go:29: judged against /var/lib/build-agent/workspace/check/mesh-host as cloned beside this check genesis_template_test.go:39: the installer's user list does not let the controller publish [mesh.seat.mesh-delivery.tool.groups] — it would come up and be refused on the first thing it tried FAIL github.com/novox/mesh-controller/internal/broker 3.557s ```
Author
Contributor

Merge check at 71b3aeaf

  • 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
  • grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine
  • read by no module's build: cmd/mesh-controller/batches_test.go, cmd/mesh-controller/issue459_test.go, cmd/mesh-controller/lone_merge_test.go, internal/broker/testdata/composed.conf, testdata/beside/CAPTURED, testdata/beside/mesh-host/examples/foundation-first-node-nats.lock, testdata/beside/mesh-host/internal/apply/placement_guard.go.captured

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

--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 57 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-12T11:32:09Z 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-12T11:32:09Z

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

notes:
  - cmd/mesh-controller/batches_test.go, cmd/mesh-controller/issue459_test.go, cmd/mesh-controller/lone_merge_test.go, internal/broker/testdata/composed.conf, testdata/beside/CAPTURED, testdata/beside/mesh-host/examples/foundation-first-node-nats.lock and testdata/beside/mesh-host/internal/apply/placement_guard.go.captured 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.044s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	247.993s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.018s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.027s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.021s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.162s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.053s
?   	github.com/novox/mesh-controller/internal/beside	[no test files]
ok  	github.com/novox/mesh-controller/internal/broker	4.083s
ok  	github.com/novox/mesh-controller/internal/builder	14.899s
ok  	github.com/novox/mesh-controller/internal/catalogue	6.968s
ok  	github.com/novox/mesh-controller/internal/conditions	2.433s
ok  	github.com/novox/mesh-controller/internal/envfile	1.021s
ok  	github.com/novox/mesh-controller/internal/facts	1.022s
ok  	github.com/novox/mesh-controller/internal/identity	4.787s
ok  	github.com/novox/mesh-controller/internal/inventory	86.844s
ok  	github.com/novox/mesh-controller/internal/lease	17.710s
ok  	github.com/novox/mesh-controller/internal/licences	4.360s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.008s
ok  	github.com/novox/mesh-controller/internal/link	58.992s
ok  	github.com/novox/mesh-controller/internal/lint	2.253s
ok  	github.com/novox/mesh-controller/internal/outward	1.035s
ok  	github.com/novox/mesh-controller/internal/overlay	1.034s
ok  	github.com/novox/mesh-controller/internal/secrets	1.463s
ok  	github.com/novox/mesh-controller/internal/store	3.272s
ok  	github.com/novox/mesh-controller/internal/testbus	1.192s
ok  	github.com/novox/mesh-controller/internal/token	1.014s
store tests, each run against the store:
  ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.35s)
  ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.36s)
  ./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.35s)
  ./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.34s)
  ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.34s)
  ./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.32s)
  ./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.37s)
  ./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.21s)
  ./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.20s)
  ./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.22s)
  ./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.21s)
**Merge check** at `71b3aeaf` - `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 - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine - read by no module's build: cmd/mesh-controller/batches_test.go, cmd/mesh-controller/issue459_test.go, cmd/mesh-controller/lone_merge_test.go, internal/broker/testdata/composed.conf, testdata/beside/CAPTURED, testdata/beside/mesh-host/examples/foundation-first-node-nats.lock, testdata/beside/mesh-host/internal/apply/placement_guard.go.captured Run by the build seat on g14 as `build-1791804753250746450` (`builds --log build-1791804753250746450`). ``` --- the gate: build-agent, mesh-controller, route-proxy mesh-controller: ok, 57 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-12T11:32:09Z 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-12T11:32:09Z 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 notes: - cmd/mesh-controller/batches_test.go, cmd/mesh-controller/issue459_test.go, cmd/mesh-controller/lone_merge_test.go, internal/broker/testdata/composed.conf, testdata/beside/CAPTURED, testdata/beside/mesh-host/examples/foundation-first-node-nats.lock and testdata/beside/mesh-host/internal/apply/placement_guard.go.captured 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.044s ok github.com/novox/mesh-controller/cmd/mesh-controller 247.993s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.018s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.027s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.021s ok github.com/novox/mesh-controller/examples/route-proxy 1.162s ok github.com/novox/mesh-controller/internal/artifacts 1.053s ? github.com/novox/mesh-controller/internal/beside [no test files] ok github.com/novox/mesh-controller/internal/broker 4.083s ok github.com/novox/mesh-controller/internal/builder 14.899s ok github.com/novox/mesh-controller/internal/catalogue 6.968s ok github.com/novox/mesh-controller/internal/conditions 2.433s ok github.com/novox/mesh-controller/internal/envfile 1.021s ok github.com/novox/mesh-controller/internal/facts 1.022s ok github.com/novox/mesh-controller/internal/identity 4.787s ok github.com/novox/mesh-controller/internal/inventory 86.844s ok github.com/novox/mesh-controller/internal/lease 17.710s ok github.com/novox/mesh-controller/internal/licences 4.360s ok github.com/novox/mesh-controller/internal/licences/adapters 1.008s ok github.com/novox/mesh-controller/internal/link 58.992s ok github.com/novox/mesh-controller/internal/lint 2.253s ok github.com/novox/mesh-controller/internal/outward 1.035s ok github.com/novox/mesh-controller/internal/overlay 1.034s ok github.com/novox/mesh-controller/internal/secrets 1.463s ok github.com/novox/mesh-controller/internal/store 3.272s ok github.com/novox/mesh-controller/internal/testbus 1.192s ok github.com/novox/mesh-controller/internal/token 1.014s store tests, each run against the store: ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.35s) ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.36s) ./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.35s) ./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.34s) ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.34s) ./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.32s) ./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.37s) ./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.21s) ./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.20s) ./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.22s) ./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.21s) ```
mesh-admin merged commit 4b1dee6b79 into main 2026-10-12 11:46:59 +00:00
mesh-admin deleted branch feat/525-a-lone-merge-skips-the-window 2026-10-12 11:46:59 +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#250