mesh-delivery: give a waiting walk its word or say what holds it (issues 529, 362) #229

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

Fixes the mesh-delivery side of novox/hq issue 529, and the nzbgeek case in issue 362's note of 2026-10-11.

The nzbgeek case. A merge whose plan builds a new module and sends it nowhere is delivered at once (published → delivered, "nothing for a walk to move", table.go's Published/EvDone row). The controller can still open a walk for it, for example when the module was placed on a machine after its plan was made. Ended deliveries are never tied to a walk (answers.go deliveriesWalking), and accounted stops the walk being adopted, so nothing gave it its word: it waited 39 minutes and queued two walks behind it. Now a waiting walk that answers only merges whose deliveries ended delivered with nothing for a walk to move is given its word (nothingToMoveWords, answers.go). A walk that also names a merge this owner holds no such delivery for is left alone.

The telling.

  • delivery_status lists each held delivery under held: id, since when, its reason, its waiting walk, and mesh-delivery.release / mesh-delivery.stop. Before, it gave only a count.
  • stalled with walks: true returns, for each walk waiting for this owner's word, what holds it: the held delivery and its reason (state held), the deliveries not at their turn (state published, what was said only in the journal), or that no live delivery holds it (unheld). Without the argument, stalled is unchanged, so the self-check raises no new condition. The controller's plans reads it (mesh-controller PR on the same branch).

Tests (issue529_test.go). These failed on main: TestAWalkAnsweringOnlyNothingToMoveMergesIsGivenItsWord (the 21:43 case), TestAWalkOfANothingToMoveMergesOwnCommitIsGivenItsWord, TestTheWordForANothingToMoveWalkSaysWhy and TestTheStatusNamesAHeldDeliveryAndWhy. TestAWaitingWalkIsToldWhatHoldsIt and TestAWaitingWalkSaysWhichDeliveryIsNotAtItsTurn did not compile on main. go vet, go test -race and merge-check.sh for modules/mesh-delivery pass.

Merge order. This PR and mesh-controller's share a branch name, so they form one delivery group. Merge only once the group's composed check has passed for both heads. Either order works: the controller reads stalled with walks and falls back to the old line when the owner does not answer it. Merging this one first means the controller's line is complete as soon as it lands.

Fixes the mesh-delivery side of novox/hq issue 529, and the nzbgeek case in issue 362's note of 2026-10-11. **The nzbgeek case.** A merge whose plan builds a new module and sends it nowhere is delivered at once (`published → delivered`, "nothing for a walk to move", table.go's Published/EvDone row). The controller can still open a walk for it, for example when the module was placed on a machine after its plan was made. Ended deliveries are never tied to a walk (answers.go `deliveriesWalking`), and `accounted` stops the walk being adopted, so nothing gave it its word: it waited 39 minutes and queued two walks behind it. Now a waiting walk that answers only merges whose deliveries ended delivered with nothing for a walk to move is given its word (`nothingToMoveWords`, answers.go). A walk that also names a merge this owner holds no such delivery for is left alone. **The telling.** - `delivery_status` lists each held delivery under `held`: id, since when, its reason, its waiting walk, and `mesh-delivery.release` / `mesh-delivery.stop`. Before, it gave only a count. - `stalled` with `walks: true` returns, for each walk waiting for this owner's word, what holds it: the held delivery and its reason (state `held`), the deliveries not at their turn (state `published`, what was said only in the journal), or that no live delivery holds it (`unheld`). Without the argument, `stalled` is unchanged, so the self-check raises no new condition. The controller's `plans` reads it (mesh-controller PR on the same branch). **Tests** (`issue529_test.go`). These failed on main: `TestAWalkAnsweringOnlyNothingToMoveMergesIsGivenItsWord` (the 21:43 case), `TestAWalkOfANothingToMoveMergesOwnCommitIsGivenItsWord`, `TestTheWordForANothingToMoveWalkSaysWhy` and `TestTheStatusNamesAHeldDeliveryAndWhy`. `TestAWaitingWalkIsToldWhatHoldsIt` and `TestAWaitingWalkSaysWhichDeliveryIsNotAtItsTurn` did not compile on main. `go vet`, `go test -race` and `merge-check.sh` for modules/mesh-delivery pass. **Merge order.** This PR and mesh-controller's share a branch name, so they form one delivery group. Merge only once the group's composed check has passed for both heads. Either order works: the controller reads `stalled` with `walks` and falls back to the old line when the owner does not answer it. Merging this one first means the controller's line is complete as soon as it lands.
mesh-admin added 1 commit 2026-10-12 09:27:28 +00:00
Give a waiting walk its word or say what holds it (issues 529, 362)
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
mesh/merge-gate pass: builds mesh-delivery → 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, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
2bee70a478
A merge whose plan sends nothing is delivered at once, yet the controller
can still open a walk for it; no live delivery then held the walk and it
waited for a person (the nzbgeek case). Give such a walk its word.

Name each held delivery in the status, and let stalled say, for every
waiting walk, what holds it, so the controller's plans line points at the
person's decision instead of a hand start.
Author
Contributor

Delivery novox/mesh-catalog@1de89cd70204 — delivered since 2026-10-12T10:02:18Z

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

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

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

Machines

  • mesh-delivery on novox: passed — carried by release-1791799070012484957
  • mesh-controller on novox: passed — 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:34 (new) → proposed (announced): novox/mesh-catalog#229's head announced
  • 2026-10-12 09:37 proposed → checked (checked): the verdict names this commit
  • 2026-10-12 09:37 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-catalog@1de89cd70204` — **delivered** since 2026-10-12T10:02:18Z **Delivery plan** — builds mesh-delivery → novox; no bus step - tier 0: mesh-delivery - novox: receives mesh-delivery **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-delivery on novox: passed — carried by release-1791799070012484957 - mesh-controller on novox: passed — 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:34 (new) → proposed (announced): novox/mesh-catalog#229's head announced - 2026-10-12 09:37 proposed → checked (checked): the verdict names this commit - 2026-10-12 09:37 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`.
Author
Contributor

Merge check at 2bee70a4

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-delivery)
  • mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

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

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

Run by the build seat on ace as build-1791797255462327502 (builds --log build-1791797255462327502).

--- the gate: mesh-delivery
mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, gitea.gitea_open_pulls, keeps state deliveries, groups
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-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

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-delivery

notes:
  - modules/mesh-delivery/cmd/mesh-delivery/issue529_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.003s
words: 12 retired words and 70 daemons' lines, none in the 42326 strings of 682 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.012s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/mesh-delivery
ok  	mesh-delivery/cmd/mesh-delivery	2.318s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `2bee70a4` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-delivery) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds mesh-delivery → novox; no bus step - tier 0: mesh-delivery - novox: receives mesh-delivery - read by no module's build: modules/mesh-delivery/cmd/mesh-delivery/issue529_test.go Run by the build seat on ace as `build-1791797255462327502` (`builds --log build-1791797255462327502`). ``` --- the gate: mesh-delivery mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, gitea.gitea_open_pulls, keeps state deliveries, groups long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-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 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-delivery notes: - modules/mesh-delivery/cmd/mesh-delivery/issue529_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.003s words: 12 retired words and 70 daemons' lines, none in the 42326 strings of 682 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 69, as kept testing modules/mesh-delivery ok mesh-delivery/cmd/mesh-delivery 2.318s --- its merge-check-typescript.sh (typescript toolchain) ```
jschoubben added 1 commit 2026-10-12 09:33:55 +00:00
Name a walk of nothing-to-move merges instead of letting it go (issue 529)
mesh/delivery delivered
mesh/merge-gate pass: builds mesh-delivery → 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, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery-group group fix/529-a-waiting-walk-is-answered-or-named merged: every member is merged
1de89cd702
The review showed the give-the-word rule skipped a failed or missing check
and group order, and let go moves nothing judged; to-be 47 has no such path.
Such a walk is now said, by stalled with walks, as held by nothing, why.
Author
Contributor

Revised at 1de89cd7, after review. The give-the-word rule is removed (answeredMovingNothing, nothingToMoveWords, their call in plan() and their tests). It would have let go a walk whose merge's check failed or never ran, or whose group mate was unchecked, and it let go moves nothing had judged. To-be 47 has no such path. The description above is out of date on that point.

What remains:

  • the held list in delivery_status;
  • stalled with walks: true.

A walk of the nzbgeek shape is now said there as unheld (held by nothing), with the reason "its merges' deliveries ended as nothing-to-move (), yet the walk moves ". The new test is TestAWalkOfNothingToMoveMergesIsNamedAsHeldByNothing, which does not compile on main. Adopting such a walk as a delivery of its own, as the design says, stays open on issue 529.

Revised at 1de89cd7, after review. **The give-the-word rule is removed** (`answeredMovingNothing`, `nothingToMoveWords`, their call in `plan()` and their tests). It would have let go a walk whose merge's check failed or never ran, or whose group mate was unchecked, and it let go moves nothing had judged. To-be 47 has no such path. The description above is out of date on that point. What remains: - the `held` list in `delivery_status`; - `stalled` with `walks: true`. A walk of the nzbgeek shape is now said there as `unheld` (held by nothing), with the reason "its merges' deliveries ended as nothing-to-move (<ids>), yet the walk moves <modules>". The new test is `TestAWalkOfNothingToMoveMergesIsNamedAsHeldByNothing`, which does not compile on main. Adopting such a walk as a delivery of its own, as the design says, stays open on issue 529.
Author
Contributor

Merge check at 1de89cd7

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-delivery)
  • mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

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

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

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

--- the gate: mesh-delivery
mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, gitea.gitea_open_pulls, keeps state deliveries, groups
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-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

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-delivery

notes:
  - modules/mesh-delivery/cmd/mesh-delivery/issue529_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.004s
words: 12 retired words and 70 daemons' lines, none in the 42326 strings of 682 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.011s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.005s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/mesh-delivery
ok  	mesh-delivery/cmd/mesh-delivery	2.327s
--- its merge-check-typescript.sh (typescript toolchain)
Unable to find image 'novox.internal:5100/mesh-tools/build@sha256:a2fe1c48ed3ce47f3fad530e864df286b1c1df487c5f188acbb9331c3f77b648' locally
novox.internal:5100/mesh-tools/build@sha256:a2fe1c48ed3ce47f3fad530e864df286b1c1df487c5f188acbb9331c3f77b648: Pulling from mesh-tools/build
501c3e032d32: Already exists
d456d1aa143e: Already exists
60f37e2c93ec: Already exists
e53f92c42dd6: Already exists
b571db164614: Already exists
c2fe729cfd79: Pulling fs layer
1d413f02b2bb: Pulling fs layer
5425cbfa56d8: Pulling fs layer
3f33de9211f7: Pulling fs layer
4511d3b71221: Pulling fs layer
95acc50ca92f: Pulling fs layer
263d412ee717: Pulling fs layer
39d54704a123: Pulling fs layer
d6dd8b11b641: Pulling fs layer
95acc50ca92f: Waiting
263d412ee717: Waiting
d6dd8b11b641: Waiting
39d54704a123: Waiting
3f33de9211f7: Waiting
4511d3b71221: Waiting
c2fe729cfd79: Download complete
c2fe729cfd79: Pull complete
3f33de9211f7: Download complete
1d413f02b2bb: Pull complete
4511d3b71221: Download complete
263d412ee717: Verifying Checksum
263d412ee717: Download complete
39d54704a123: Download complete
95acc50ca92f: Download complete
5425cbfa56d8: Download complete
5425cbfa56d8: Pull complete
3f33de9211f7: Pull complete
4511d3b71221: Pull complete
95acc50ca92f: Pull complete
263d412ee717: Pull complete
39d54704a123: Pull complete
d6dd8b11b641: Verifying Checksum
d6dd8b11b641: Download complete
d6dd8b11b641: Pull complete
Digest: sha256:a2fe1c48ed3ce47f3fad530e864df286b1c1df487c5f188acbb9331c3f77b648
Status: Downloaded newer image for novox.internal:5100/mesh-tools/build@sha256:a2fe1c48ed3ce47f3fad530e864df286b1c1df487c5f188acbb9331c3f77b648
**Merge check** at `1de89cd7` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-delivery) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds mesh-delivery → novox; no bus step - tier 0: mesh-delivery - novox: receives mesh-delivery - read by no module's build: modules/mesh-delivery/cmd/mesh-delivery/issue529_test.go Run by the build seat on g14 as `build-1791797659624166214` (`builds --log build-1791797659624166214`). ``` --- the gate: mesh-delivery mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-order, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, gitea.gitea_open_pulls, keeps state deliveries, groups long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-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 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-delivery notes: - modules/mesh-delivery/cmd/mesh-delivery/issue529_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.004s words: 12 retired words and 70 daemons' lines, none in the 42326 strings of 682 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.011s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/paths 0.005s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 69, as kept testing modules/mesh-delivery ok mesh-delivery/cmd/mesh-delivery 2.327s --- its merge-check-typescript.sh (typescript toolchain) Unable to find image 'novox.internal:5100/mesh-tools/build@sha256:a2fe1c48ed3ce47f3fad530e864df286b1c1df487c5f188acbb9331c3f77b648' locally novox.internal:5100/mesh-tools/build@sha256:a2fe1c48ed3ce47f3fad530e864df286b1c1df487c5f188acbb9331c3f77b648: Pulling from mesh-tools/build 501c3e032d32: Already exists d456d1aa143e: Already exists 60f37e2c93ec: Already exists e53f92c42dd6: Already exists b571db164614: Already exists c2fe729cfd79: Pulling fs layer 1d413f02b2bb: Pulling fs layer 5425cbfa56d8: Pulling fs layer 3f33de9211f7: Pulling fs layer 4511d3b71221: Pulling fs layer 95acc50ca92f: Pulling fs layer 263d412ee717: Pulling fs layer 39d54704a123: Pulling fs layer d6dd8b11b641: Pulling fs layer 95acc50ca92f: Waiting 263d412ee717: Waiting d6dd8b11b641: Waiting 39d54704a123: Waiting 3f33de9211f7: Waiting 4511d3b71221: Waiting c2fe729cfd79: Download complete c2fe729cfd79: Pull complete 3f33de9211f7: Download complete 1d413f02b2bb: Pull complete 4511d3b71221: Download complete 263d412ee717: Verifying Checksum 263d412ee717: Download complete 39d54704a123: Download complete 95acc50ca92f: Download complete 5425cbfa56d8: Download complete 5425cbfa56d8: Pull complete 3f33de9211f7: Pull complete 4511d3b71221: Pull complete 95acc50ca92f: Pull complete 263d412ee717: Pull complete 39d54704a123: Pull complete d6dd8b11b641: Verifying Checksum d6dd8b11b641: Download complete d6dd8b11b641: Pull complete Digest: sha256:a2fe1c48ed3ce47f3fad530e864df286b1c1df487c5f188acbb9331c3f77b648 Status: Downloaded newer image for novox.internal:5100/mesh-tools/build@sha256:a2fe1c48ed3ce47f3fad530e864df286b1c1df487c5f188acbb9331c3f77b648 ```
mesh-admin merged commit da296cacc6 into main 2026-10-12 09:55:21 +00:00
mesh-admin deleted branch fix/529-a-waiting-walk-is-answered-or-named 2026-10-12 09:55:22 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#229