plans names the hold a waiting walk waits on (issue 529) #245

Merged
mesh-admin merged 2 commits from fix/529-a-waiting-walk-is-answered-or-named into main 2026-10-12 09:55:18 +00:00
Contributor

Fixes the controller side of novox/hq issue 529, note 2.

Cause. waitingNote (cmd/mesh-controller/delivery.go) says the same line for every walk that waits for mesh-delivery's word: "published; its walk waits for mesh-delivery's word — plans go … --why … starts it by hand". When the delivery was held for a person (here mesh-sdk #22, merged before its group's composed check passed), that line pointed the reader at a hand start instead of at the person's decision.

Change.

  • plans and plans <id> ask mesh-delivery once, with a 3 s bound and only when a listed walk waits, what holds each waiting walk: its stalled verb with walks: true (walksWaiting, waitsOf). The controller's grant already names stalled, so no bus credential changes.
  • planLineSaid / waitingSaid: a walk whose carried delivery is held reads "its walk waits for mesh-delivery's word, and a delivery it carries is held for a person: held since …: — a person decides: mesh-delivery.release (id …, why) lets it go, mesh-delivery.stop ends it". A walk waiting because a delivery is not at its turn names that delivery. If mesh-delivery says nothing (an older owner, none answering, the bus down), the line reads as before.
  • stalledLine reads the walk field.

Tests (issue529_test.go): TestAWalkWaitingOnAHeldDeliveryNamesTheHold, TestAWalkWaitingOnADeliveryNotAtItsTurnSaysSo and TestWhatHoldsTheWaitingWalksIsAskedOfTheDeliveryOwner. All three fail on main, where they do not compile. go vet ./... and go test -race ./cmd/mesh-controller pass. No store test is needed.

Merge order. mesh-catalog #229 (mesh-delivery's stalled with walks) is on the same branch, so the two form one delivery group. Merge only once the group's composed check has passed for both heads. #229 first is preferred, because then this line is complete as soon as it lands. Either order is safe. This is a controller rollout, so merge it only while mesh-controller.plans says no plan is mid-gate.

Fixes the controller side of novox/hq issue 529, note 2. **Cause.** `waitingNote` (cmd/mesh-controller/delivery.go) says the same line for every walk that waits for mesh-delivery's word: "published; its walk waits for mesh-delivery's word — `plans go … --why …` starts it by hand". When the delivery was held for a person (here mesh-sdk #22, merged before its group's composed check passed), that line pointed the reader at a hand start instead of at the person's decision. **Change.** - `plans` and `plans <id>` ask mesh-delivery once, with a 3 s bound and only when a listed walk waits, what holds each waiting walk: its `stalled` verb with `walks: true` (`walksWaiting`, `waitsOf`). The controller's grant already names `stalled`, so no bus credential changes. - `planLineSaid` / `waitingSaid`: a walk whose carried delivery is held reads "its walk waits for mesh-delivery's word, and a delivery it carries is held for a person: <id> held since …: <reason> — a person decides: `mesh-delivery.release` (id …, why) lets it go, `mesh-delivery.stop` ends it". A walk waiting because a delivery is not at its turn names that delivery. If mesh-delivery says nothing (an older owner, none answering, the bus down), the line reads as before. - `stalledLine` reads the `walk` field. **Tests** (`issue529_test.go`): `TestAWalkWaitingOnAHeldDeliveryNamesTheHold`, `TestAWalkWaitingOnADeliveryNotAtItsTurnSaysSo` and `TestWhatHoldsTheWaitingWalksIsAskedOfTheDeliveryOwner`. All three fail on main, where they do not compile. `go vet ./...` and `go test -race ./cmd/mesh-controller` pass. No store test is needed. **Merge order.** mesh-catalog #229 (mesh-delivery's `stalled` with `walks`) is on the same branch, so the two form one delivery group. Merge only once the group's composed check has passed for both heads. #229 first is preferred, because then this line is complete as soon as it lands. Either order is safe. This is a controller rollout, so merge it only while `mesh-controller.plans` says no plan is mid-gate.
mesh-admin added 1 commit 2026-10-12 09:27:39 +00:00
Name the hold a waiting walk waits on in plans (issue 529)
mesh/merge-gate pass: builds mesh-controller → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery superseded: a newer head of the same pull request
mesh/delivery-group group fix/529-a-waiting-walk-is-answered-or-named checking: 0 of 2 member(s) ready
ed037784e2
A walk whose delivery was held for a person said only that it waits for
mesh-delivery's word and that plans go starts it by hand, pointing the
reader at a hand start instead of the person's decision. Ask mesh-delivery
what holds each waiting walk and say the held delivery, its reason and
mesh-delivery.release, or the delivery not at its turn.
Author
Contributor

Delivery novox/mesh-controller@b03ec3b64e81 — delivered since 2026-10-12T10:02:18Z

Delivery plan — builds mesh-controller → novox; no bus step

  • tier 0: mesh-controller
  • novox: receives mesh-controller

Group fix/529-a-waiting-walk-is-answered-or-named, in order: novox/mesh-controller@b03ec3b64e → novox/mesh-catalog@1de89cd702

Machines

  • mesh-controller on novox: passed — healthy 3 times over 3m40s
  • mesh-delivery on novox: passed — judged with mesh-controller: healthy 3 times over 3m40s
  • mesh-controller on the rest running it: sent
  • mesh-delivery on the rest running it: sent

Transitions

  • 2026-10-12 09:35 (new) → proposed (announced): novox/mesh-controller#245's head announced
  • 2026-10-12 09:42 proposed → checked (checked): the verdict names this commit
  • 2026-10-12 09:42 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-12 09:57 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 09:57 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 10: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@b03ec3b64e81` — **delivered** since 2026-10-12T10:02:18Z **Delivery plan** — builds mesh-controller → novox; no bus step - tier 0: mesh-controller - novox: receives mesh-controller **Group** `fix/529-a-waiting-walk-is-answered-or-named`, in order: novox/mesh-controller@b03ec3b64e81 → novox/mesh-catalog@1de89cd70204 - novox/mesh-controller@b03ec3b64e81 before novox/mesh-catalog@1de89cd70204: version skew - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **Machines** - mesh-controller on novox: passed — healthy 3 times over 3m40s - mesh-delivery on novox: passed — judged with mesh-controller: healthy 3 times over 3m40s - mesh-controller on the rest running it: sent - mesh-delivery on the rest running it: sent **Transitions** - 2026-10-12 09:35 (new) → proposed (announced): novox/mesh-controller#245's head announced - 2026-10-12 09:42 proposed → checked (checked): the verdict names this commit - 2026-10-12 09:42 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-12 09:57 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 09:57 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 10: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`.
jschoubben added 1 commit 2026-10-12 09:34:56 +00:00
Offer no hand start for a walk that is only waiting its turn (issue 529)
mesh/merge-gate pass: builds mesh-controller → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery delivered
mesh/delivery-group group fix/529-a-waiting-walk-is-answered-or-named merged: every member is merged
b03ec3b64e
A hand start there would skip its group's order; point at it only for a
walk nothing holds, and say why nothing holds it.
Author
Contributor

Merge check at ed037784

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

Delivery plan — builds mesh-controller → novox; no bus step

  • tier 0: mesh-controller
  • novox: receives mesh-controller
  • read by no module's build: cmd/mesh-controller/issue529_test.go

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

--- the gate: mesh-controller
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-12T09:19:13Z 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-12T09:19:13Z

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 1 module(s) in 1 tier(s): mesh-controller

notes:
  - cmd/mesh-controller/issue529_test.go 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	262.007s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.041s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.066s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.036s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.224s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.092s
?   	github.com/novox/mesh-controller/internal/beside	[no test files]
ok  	github.com/novox/mesh-controller/internal/broker	4.590s
ok  	github.com/novox/mesh-controller/internal/builder	19.690s
ok  	github.com/novox/mesh-controller/internal/catalogue	8.730s
ok  	github.com/novox/mesh-controller/internal/conditions	2.668s
ok  	github.com/novox/mesh-controller/internal/envfile	1.054s
ok  	github.com/novox/mesh-controller/internal/facts	1.043s
ok  	github.com/novox/mesh-controller/internal/identity	5.178s
ok  	github.com/novox/mesh-controller/internal/inventory	106.183s
ok  	github.com/novox/mesh-controller/internal/lease	17.737s
ok  	github.com/novox/mesh-controller/internal/licences	4.692s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.059s
ok  	github.com/novox/mesh-controller/internal/link	63.362s
ok  	github.com/novox/mesh-controller/internal/lint	2.498s
ok  	github.com/novox/mesh-controller/internal/outward	1.099s
ok  	github.com/novox/mesh-controller/internal/overlay	1.091s
ok  	github.com/novox/mesh-controller/internal/secrets	1.582s
ok  	github.com/novox/mesh-controller/internal/store	3.624s
ok  	github.com/novox/mesh-controller/internal/testbus	1.270s
ok  	github.com/novox/mesh-controller/internal/token	1.015s
store tests, each run against the store:
  ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.46s)
  ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.47s)
  ./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.43s)
  ./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.43s)
  ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.40s)
  ./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.38s)
  ./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.45s)
  ./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.27s)
  ./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.26s)
  ./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.28s)
  ./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.26s)
**Merge check** at `ed037784` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds mesh-controller → novox; no bus step - tier 0: mesh-controller - novox: receives mesh-controller - read by no module's build: cmd/mesh-controller/issue529_test.go Run by the build seat on shanks as `build-1791797285905808357` (`builds --log build-1791797285905808357`). ``` --- the gate: mesh-controller 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-12T09:19:13Z 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-12T09:19:13Z 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 1 module(s) in 1 tier(s): mesh-controller notes: - cmd/mesh-controller/issue529_test.go 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 262.007s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.041s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.066s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.036s ok github.com/novox/mesh-controller/examples/route-proxy 1.224s ok github.com/novox/mesh-controller/internal/artifacts 1.092s ? github.com/novox/mesh-controller/internal/beside [no test files] ok github.com/novox/mesh-controller/internal/broker 4.590s ok github.com/novox/mesh-controller/internal/builder 19.690s ok github.com/novox/mesh-controller/internal/catalogue 8.730s ok github.com/novox/mesh-controller/internal/conditions 2.668s ok github.com/novox/mesh-controller/internal/envfile 1.054s ok github.com/novox/mesh-controller/internal/facts 1.043s ok github.com/novox/mesh-controller/internal/identity 5.178s ok github.com/novox/mesh-controller/internal/inventory 106.183s ok github.com/novox/mesh-controller/internal/lease 17.737s ok github.com/novox/mesh-controller/internal/licences 4.692s ok github.com/novox/mesh-controller/internal/licences/adapters 1.059s ok github.com/novox/mesh-controller/internal/link 63.362s ok github.com/novox/mesh-controller/internal/lint 2.498s ok github.com/novox/mesh-controller/internal/outward 1.099s ok github.com/novox/mesh-controller/internal/overlay 1.091s ok github.com/novox/mesh-controller/internal/secrets 1.582s ok github.com/novox/mesh-controller/internal/store 3.624s ok github.com/novox/mesh-controller/internal/testbus 1.270s ok github.com/novox/mesh-controller/internal/token 1.015s store tests, each run against the store: ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.46s) ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.47s) ./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.43s) ./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.43s) ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.40s) ./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.38s) ./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.45s) ./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.27s) ./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.26s) ./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.28s) ./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.26s) ```
Author
Contributor

Revised at b03ec3b6, after review. A walk whose delivery is only not at its turn no longer ends with "plans go … starts it by hand", because a hand start there would skip its group's order. The hand start is offered only for a walk nothing holds, and the line now says why nothing holds it (for example, its merges' deliveries ended as nothing-to-move). New test: TestAWalkHeldByNothingSaysWhyAndTheHandStart.

Revised at b03ec3b6, after review. A walk whose delivery is only not at its turn no longer ends with "`plans go …` starts it by hand", because a hand start there would skip its group's order. The hand start is offered only for a walk nothing holds, and the line now says why nothing holds it (for example, its merges' deliveries ended as nothing-to-move). New test: `TestAWalkHeldByNothingSaysWhyAndTheHandStart`.
Author
Contributor

Merge check at b03ec3b6

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

Delivery plan — builds mesh-controller → novox; no bus step

  • tier 0: mesh-controller
  • novox: receives mesh-controller
  • read by no module's build: cmd/mesh-controller/issue529_test.go

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

--- the gate: mesh-controller
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-12T09:19:13Z 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-12T09:19:13Z

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 1 module(s) in 1 tier(s): mesh-controller

notes:
  - cmd/mesh-controller/issue529_test.go 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	254.181s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.057s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.072s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.024s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.289s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.100s
?   	github.com/novox/mesh-controller/internal/beside	[no test files]
ok  	github.com/novox/mesh-controller/internal/broker	4.645s
ok  	github.com/novox/mesh-controller/internal/builder	19.509s
ok  	github.com/novox/mesh-controller/internal/catalogue	8.720s
ok  	github.com/novox/mesh-controller/internal/conditions	2.736s
ok  	github.com/novox/mesh-controller/internal/envfile	1.072s
ok  	github.com/novox/mesh-controller/internal/facts	1.059s
ok  	github.com/novox/mesh-controller/internal/identity	5.276s
ok  	github.com/novox/mesh-controller/internal/inventory	101.129s
ok  	github.com/novox/mesh-controller/internal/lease	17.753s
ok  	github.com/novox/mesh-controller/internal/licences	4.850s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.075s
ok  	github.com/novox/mesh-controller/internal/link	62.218s
ok  	github.com/novox/mesh-controller/internal/lint	2.583s
ok  	github.com/novox/mesh-controller/internal/outward	1.107s
ok  	github.com/novox/mesh-controller/internal/overlay	1.098s
ok  	github.com/novox/mesh-controller/internal/secrets	1.586s
ok  	github.com/novox/mesh-controller/internal/store	3.615s
ok  	github.com/novox/mesh-controller/internal/testbus	1.286s
ok  	github.com/novox/mesh-controller/internal/token	1.019s
store tests, each run against the store:
  ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.42s)
  ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.44s)
  ./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.42s)
  ./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.42s)
  ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.51s)
  ./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.38s)
  ./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.45s)
  ./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.26s)
  ./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.26s)
  ./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.27s)
  ./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.26s)
**Merge check** at `b03ec3b6` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds mesh-controller → novox; no bus step - tier 0: mesh-controller - novox: receives mesh-controller - read by no module's build: cmd/mesh-controller/issue529_test.go Run by the build seat on shanks as `build-1791797722006793821` (`builds --log build-1791797722006793821`). ``` --- the gate: mesh-controller 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-12T09:19:13Z 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-12T09:19:13Z 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 1 module(s) in 1 tier(s): mesh-controller notes: - cmd/mesh-controller/issue529_test.go 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 254.181s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.057s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.072s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.024s ok github.com/novox/mesh-controller/examples/route-proxy 1.289s ok github.com/novox/mesh-controller/internal/artifacts 1.100s ? github.com/novox/mesh-controller/internal/beside [no test files] ok github.com/novox/mesh-controller/internal/broker 4.645s ok github.com/novox/mesh-controller/internal/builder 19.509s ok github.com/novox/mesh-controller/internal/catalogue 8.720s ok github.com/novox/mesh-controller/internal/conditions 2.736s ok github.com/novox/mesh-controller/internal/envfile 1.072s ok github.com/novox/mesh-controller/internal/facts 1.059s ok github.com/novox/mesh-controller/internal/identity 5.276s ok github.com/novox/mesh-controller/internal/inventory 101.129s ok github.com/novox/mesh-controller/internal/lease 17.753s ok github.com/novox/mesh-controller/internal/licences 4.850s ok github.com/novox/mesh-controller/internal/licences/adapters 1.075s ok github.com/novox/mesh-controller/internal/link 62.218s ok github.com/novox/mesh-controller/internal/lint 2.583s ok github.com/novox/mesh-controller/internal/outward 1.107s ok github.com/novox/mesh-controller/internal/overlay 1.098s ok github.com/novox/mesh-controller/internal/secrets 1.586s ok github.com/novox/mesh-controller/internal/store 3.615s ok github.com/novox/mesh-controller/internal/testbus 1.286s ok github.com/novox/mesh-controller/internal/token 1.019s store tests, each run against the store: ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.42s) ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.44s) ./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.42s) ./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.42s) ./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.51s) ./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.38s) ./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.45s) ./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.26s) ./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.26s) ./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.27s) ./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.26s) ```
mesh-admin merged commit 22a2f73f7b into main 2026-10-12 09:55:18 +00:00
mesh-admin deleted branch fix/529-a-waiting-walk-is-answered-or-named 2026-10-12 09:55:18 +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#245