novox/mesh-catalog
13
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

mesh-delivery waits for nothing: a check is asked at once and a standing verdict adopted (issue 1115) #361

Merged
mesh-tools merged 4 commits from fix/zero-delay into main 2026-10-18 10:38:06 +00:00
Conversation 3 Commits 4 Files Changed 12
+276 -119
mesh-tools commented 2026-10-18 10:28:41 +00:00
Member
Copy Link
Copy Source

Issue 1115. The operator decided on 2026-10-18 at 12:20: zero delay everywhere, few guards built up front; let it fail loudly and fix it. Live: mesh-controller#379 took over its delivery at 10:01Z and stood proposed with no check asked, behind a 15-minute grace.

  • checkGrace (15 min) is removed. A proposed delivery with no verdict reads the forge's open pull requests at each look. It adopts a standing verdict when every required status (at least mesh/merge-gate and mesh/repo-check) passes at its head, and otherwise asks its check at once. A kept ask with an empty id counts as no ask. An empty answer from the controller is a refusal, said and asked again at most once a minute.
  • mergeRetryAfter (1 min) is removed: a refused merge is asked again only on an event that decides it.
  • readyRefusedFor (1 h) and groupRefusedFor (10 min) are 0: a refusal is said as stalled at once.
  • Kept, with reasons: matchGrace (2 min: a walk and its merge arrive as separate events in no fixed order), the failure backoffs (so a dead dependency is not hammered), and the stalled bounds (they say, they delay nothing).
  • New tests failed on main first; the tests of the old waits are rewritten.
  • The first merge check at 5f00244 failed on bus_test.go's group test, which waited for any check ask and caught a member's own check now asked at once. 6954467 makes it wait for the group's composed ask; the code was right.

Once delivered, it frees mesh-controller#379 at its first look: its statuses passed at 0149a3d7 at 09:50Z.

Reviewed-by: reviewer-1115@shanks at 6954467292

Issue 1115. The operator decided on 2026-10-18 at 12:20: zero delay everywhere, few guards built up front; let it fail loudly and fix it. Live: mesh-controller#379 took over its delivery at 10:01Z and stood proposed with no check asked, behind a 15-minute grace. - checkGrace (15 min) is removed. A proposed delivery with no verdict reads the forge's open pull requests at each look. It adopts a standing verdict when every required status (at least mesh/merge-gate and mesh/repo-check) passes at its head, and otherwise asks its check at once. A kept ask with an empty id counts as no ask. An empty answer from the controller is a refusal, said and asked again at most once a minute. - mergeRetryAfter (1 min) is removed: a refused merge is asked again only on an event that decides it. - readyRefusedFor (1 h) and groupRefusedFor (10 min) are 0: a refusal is said as stalled at once. - Kept, with reasons: matchGrace (2 min: a walk and its merge arrive as separate events in no fixed order), the failure backoffs (so a dead dependency is not hammered), and the stalled bounds (they say, they delay nothing). - New tests failed on main first; the tests of the old waits are rewritten. - The first merge check at 5f00244 failed on bus_test.go's group test, which waited for any check ask and caught a member's own check now asked at once. 6954467 makes it wait for the group's composed ask; the code was right. Once delivered, it frees mesh-controller#379 at its first look: its statuses passed at 0149a3d7 at 09:50Z. Reviewed-by: reviewer-1115@shanks at 69544672926421d681886a2f813ea52345d77937
mesh-tools added 3 commits 2026-10-18 10:28:42 +00:00
mesh-delivery waits for nothing: a check is asked at once and a standing verdict adopted (issue 1115) 1760b94824
mesh-delivery adopts a standing verdict only when every required check stands, at every look, and counts an ask with no id as none (issue 1115) fc9ddd9185
mesh-delivery takes an empty answer to a check ask as a refusal (issue 1115)
mesh/merge-gate head 5f002441b7f0 merged into trunk 580fadb63ecb — pass: builds mesh-delivery → novox; no bus step; every machine composes with the change …
Details
mesh/repo-check head 5f002441b7f0 merged into trunk 580fadb63ecb — fail: its merge-check.sh failed: --- FAIL: TestAGroupOfTwoWithGreenChecksGetsOneAskAndOn…
Details
mesh/delivery superseded: a newer head of the same pull request
Details
5f002441b7
mesh-tools commented 2026-10-18 10:28:44 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/mesh-catalog@695446729264 — delivered since 2026-10-18T10:39:48Z

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

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

Machines

  • mesh-delivery on every machine running it: sent

Transitions

  • 2026-10-18 10:34 (new) → proposed (announced): novox/mesh-catalog#361's head announced
  • 2026-10-18 10:37 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-18 10:37 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-18 10:38 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-18 10:38 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
  • 2026-10-18 10:39 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@695446729264` — **delivered** since 2026-10-18T10:39:48Z **Delivery plan** — builds mesh-delivery → novox; no bus step - tier 0: mesh-delivery - novox: receives mesh-delivery **Machines** - mesh-delivery on every machine running it: sent **Transitions** - 2026-10-18 10:34 (new) → proposed (announced): novox/mesh-catalog#361's head announced - 2026-10-18 10:37 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-18 10:37 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-18 10:38 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-18 10:38 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-18 10:39 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-tools commented 2026-10-18 10:32:09 +00:00
Author
Member
Copy Link
Copy Source

Merge check at 5f002441
Judged: head 5f002441b7f0 merged into trunk 580fadb63ecb; read beside it: mesh-controller 54070f5bc32b, mesh-controller-main 54070f5bc32b, mesh-host 6469e8238443, mesh-tools 7412c5b6c9c5

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-delivery)
  • mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestAGroupOfTwoWithGreenChecksGetsOneAskAndOnItsApproveBothMergeInOnePassOverARealBus (11.63s)

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/checkask_test.go, modules/mesh-delivery/cmd/mesh-delivery/fakes_test.go, modules/mesh-delivery/cmd/mesh-delivery/group_test.go, modules/mesh-delivery/cmd/mesh-delivery/holder_test.go, modules/mesh-delivery/cmd/mesh-delivery/pullkey_test.go, modules/mesh-delivery/cmd/mesh-delivery/ready_test.go, modules/mesh-delivery/cmd/mesh-delivery/timers_test.go, modules/mesh-delivery/cmd/mesh-delivery/unchecked_events_test.go

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

--- the gate: mesh-delivery
note: mesh-delivery uses the seat "operator-channel", which no module declares and the mesh does not define among the manifests given; registration judges it against the whole catalogue, and passing the declaring module's manifest too judges it here
mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-backups-again, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, seat:mesh-controller.forget-checks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, gitea.gitea_open_pulls, gitea.gitea_merge_pull_request, gitea.gitea_add_comment, seat:operator-channel.notify, keeps state deliveries, groups, asked, pulls
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-18T10:07:06Z says they run
composing every machine as the mesh is
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
composing every machine with the change
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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-18T10:07:06Z

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-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, 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/checkask_test.go, modules/mesh-delivery/cmd/mesh-delivery/fakes_test.go, modules/mesh-delivery/cmd/mesh-delivery/group_test.go, modules/mesh-delivery/cmd/mesh-delivery/holder_test.go, modules/mesh-delivery/cmd/mesh-delivery/pullkey_test.go, modules/mesh-delivery/cmd/mesh-delivery/ready_test.go, modules/mesh-delivery/cmd/mesh-delivery/timers_test.go and modules/mesh-delivery/cmd/mesh-delivery/unchecked_events_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 53793 strings of 807 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.013s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/mailstore	0.009s
mail-store: claimed only by mesh-mail
ok  	git.novox.be/novox/mesh-catalog/checks/sshdir	0.018s
~/.ssh: named only by ssh-client
ok  	git.novox.be/novox/mesh-catalog/checks/owned	0.009s
owned paths: every directory and archive says how it treats unknown files; no module declares inside another's directory
ok  	git.novox.be/novox/mesh-catalog/checks/secrets	0.014s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
ok  	git.novox.be/novox/mesh-catalog/checks/predefined	0.268s
predefined.json: 2 key(s), none removed that a module names
ok  	git.novox.be/novox/mesh-catalog/checks/config	0.016s
config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved)
ok  	git.novox.be/novox/mesh-catalog/checks/templates	0.012s
templates: no module keeps a file's text inline but the 0 listed
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: 61, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.228s
testing modules/mesh-delivery
--- FAIL: TestAGroupOfTwoWithGreenChecksGetsOneAskAndOnItsApproveBothMergeInOnePassOverARealBus (11.63s)
    bus_test.go:147: bundle: [mesh-delivery] read back 0 delivery(ies) and 0 group(s)
    bus_test.go:147: bundle: [mesh-delivery] listening: gitea.pull.updated, gitea.pull.merged, gitea.pull.closed, gitea.forge.status, gitea.forge.pull-request.edited, gitea.forge.pull-request.closed, mesh-controller.checked, mesh-controller.plan-moved
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1: (new) → proposed (announced): novox/mesh-controller#1's head announced
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2: (new) → proposed (announced): novox/mesh-catalog#2's head announced
    bus_test.go:147: bundle: [mesh-delivery] group feat/x: novox/mesh-catalog@d2d2d2d2d2d2, novox/mesh-controller@c1c1c1c1c1c1
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2: proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2: checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1: proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1: checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2: its checks passed; the operator's Approve of its merge into main is asked once it may merge
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2 waits: its group feat/x is checking: 2 of 2 member(s) ready
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1: its checks passed; the operator's Approve of its merge into main is asked once it may merge
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1 waits: its group feat/x is checking: 2 of 2 member(s) ready
    bus_test.go:147: bundle: [mesh-delivery] a composed check of feat/x (check-1) that is not the one asked: history
    bus_test.go:551: within 10s: the operator to be asked once for the group did not happen
FAIL
FAIL	mesh-delivery/cmd/mesh-delivery	20.879s
FAIL
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestAGroupOfTwoWithGreenChecksGetsOneAskAndOnItsApproveBothMergeInOnePassOverARealBus (11.63s)
    bus_test.go:147: bundle: [mesh-delivery] read back 0 delivery(ies) and 0 group(s)
    bus_test.go:147: bundle: [mesh-delivery] listening: gitea.pull.updated, gitea.pull.merged, gitea.pull.closed, gitea.forge.status, gitea.forge.pull-request.edited, gitea.forge.pull-request.closed, mesh-controller.checked, mesh-controller.plan-moved
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1: (new) → proposed (announced): novox/mesh-controller#1's head announced
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2: (new) → proposed (announced): novox/mesh-catalog#2's head announced
    bus_test.go:147: bundle: [mesh-delivery] group feat/x: novox/mesh-catalog@d2d2d2d2d2d2, novox/mesh-controller@c1c1c1c1c1c1
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2: proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2: checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1: proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1: checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2: its checks passed; the operator's Approve of its merge into main is asked once it may merge
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2 waits: its group feat/x is checking: 2 of 2 member(s) ready
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1: its checks passed; the operator's Approve of its merge into main is asked once it may merge
    bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1 waits: its group feat/x is checking: 2 of 2 member(s) ready
    bus_test.go:147: bundle: [mesh-delivery] a composed check of feat/x (check-1) that is not the one asked: history
    bus_test.go:551: within 10s: the operator to be asked once for the group did not happen
FAIL	mesh-delivery/cmd/mesh-delivery	20.879s
**Merge check** at `5f002441` Judged: head `5f002441b7f0` merged into trunk `580fadb63ecb`; read beside it: mesh-controller `54070f5bc32b`, mesh-controller-main `54070f5bc32b`, mesh-host `6469e8238443`, mesh-tools `7412c5b6c9c5` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-delivery) - `mesh/repo-check`: **FAIL** — its merge-check.sh failed: --- FAIL: TestAGroupOfTwoWithGreenChecksGetsOneAskAndOnItsApproveBothMergeInOnePassOverARealBus (11.63s) **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/checkask_test.go, modules/mesh-delivery/cmd/mesh-delivery/fakes_test.go, modules/mesh-delivery/cmd/mesh-delivery/group_test.go, modules/mesh-delivery/cmd/mesh-delivery/holder_test.go, modules/mesh-delivery/cmd/mesh-delivery/pullkey_test.go, modules/mesh-delivery/cmd/mesh-delivery/ready_test.go, modules/mesh-delivery/cmd/mesh-delivery/timers_test.go, modules/mesh-delivery/cmd/mesh-delivery/unchecked_events_test.go Run by the build seat on shanks as `build-1792319323533108453` (`builds --log build-1792319323533108453`). ``` --- the gate: mesh-delivery note: mesh-delivery uses the seat "operator-channel", which no module declares and the mesh does not define among the manifests given; registration judges it against the whole catalogue, and passing the declaring module's manifest too judges it here mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-backups-again, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, seat:mesh-controller.forget-checks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, gitea.gitea_open_pulls, gitea.gitea_merge_pull_request, gitea.gitea_add_comment, seat:operator-channel.notify, keeps state deliveries, groups, asked, pulls 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-18T10:07:06Z says they run composing every machine as the mesh is HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus composing every machine with the change HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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-18T10:07:06Z 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-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, 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/checkask_test.go, modules/mesh-delivery/cmd/mesh-delivery/fakes_test.go, modules/mesh-delivery/cmd/mesh-delivery/group_test.go, modules/mesh-delivery/cmd/mesh-delivery/holder_test.go, modules/mesh-delivery/cmd/mesh-delivery/pullkey_test.go, modules/mesh-delivery/cmd/mesh-delivery/ready_test.go, modules/mesh-delivery/cmd/mesh-delivery/timers_test.go and modules/mesh-delivery/cmd/mesh-delivery/unchecked_events_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 53793 strings of 807 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/mailstore 0.009s mail-store: claimed only by mesh-mail ok git.novox.be/novox/mesh-catalog/checks/sshdir 0.018s ~/.ssh: named only by ssh-client ok git.novox.be/novox/mesh-catalog/checks/owned 0.009s owned paths: every directory and archive says how it treats unknown files; no module declares inside another's directory ok git.novox.be/novox/mesh-catalog/checks/secrets 0.014s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) ok git.novox.be/novox/mesh-catalog/checks/predefined 0.268s predefined.json: 2 key(s), none removed that a module names ok git.novox.be/novox/mesh-catalog/checks/config 0.016s config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved) ok git.novox.be/novox/mesh-catalog/checks/templates 0.012s templates: no module keeps a file's text inline but the 0 listed 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: 61, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.228s testing modules/mesh-delivery --- FAIL: TestAGroupOfTwoWithGreenChecksGetsOneAskAndOnItsApproveBothMergeInOnePassOverARealBus (11.63s) bus_test.go:147: bundle: [mesh-delivery] read back 0 delivery(ies) and 0 group(s) bus_test.go:147: bundle: [mesh-delivery] listening: gitea.pull.updated, gitea.pull.merged, gitea.pull.closed, gitea.forge.status, gitea.forge.pull-request.edited, gitea.forge.pull-request.closed, mesh-controller.checked, mesh-controller.plan-moved bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1: (new) → proposed (announced): novox/mesh-controller#1's head announced bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2: (new) → proposed (announced): novox/mesh-catalog#2's head announced bus_test.go:147: bundle: [mesh-delivery] group feat/x: novox/mesh-catalog@d2d2d2d2d2d2, novox/mesh-controller@c1c1c1c1c1c1 bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2: proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2: checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1: proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1: checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2: its checks passed; the operator's Approve of its merge into main is asked once it may merge bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2 waits: its group feat/x is checking: 2 of 2 member(s) ready bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1: its checks passed; the operator's Approve of its merge into main is asked once it may merge bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1 waits: its group feat/x is checking: 2 of 2 member(s) ready bus_test.go:147: bundle: [mesh-delivery] a composed check of feat/x (check-1) that is not the one asked: history bus_test.go:551: within 10s: the operator to be asked once for the group did not happen FAIL FAIL mesh-delivery/cmd/mesh-delivery 20.879s FAIL --- what failed, picked from the whole of its output (the whole is in the build's log) --- FAIL: TestAGroupOfTwoWithGreenChecksGetsOneAskAndOnItsApproveBothMergeInOnePassOverARealBus (11.63s) bus_test.go:147: bundle: [mesh-delivery] read back 0 delivery(ies) and 0 group(s) bus_test.go:147: bundle: [mesh-delivery] listening: gitea.pull.updated, gitea.pull.merged, gitea.pull.closed, gitea.forge.status, gitea.forge.pull-request.edited, gitea.forge.pull-request.closed, mesh-controller.checked, mesh-controller.plan-moved bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1: (new) → proposed (announced): novox/mesh-controller#1's head announced bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2: (new) → proposed (announced): novox/mesh-catalog#2's head announced bus_test.go:147: bundle: [mesh-delivery] group feat/x: novox/mesh-catalog@d2d2d2d2d2d2, novox/mesh-controller@c1c1c1c1c1c1 bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2: proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2: checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1: proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1: checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2: its checks passed; the operator's Approve of its merge into main is asked once it may merge bus_test.go:147: bundle: [mesh-delivery] novox/mesh-catalog@d2d2d2d2d2d2 waits: its group feat/x is checking: 2 of 2 member(s) ready bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1: its checks passed; the operator's Approve of its merge into main is asked once it may merge bus_test.go:147: bundle: [mesh-delivery] novox/mesh-controller@c1c1c1c1c1c1 waits: its group feat/x is checking: 2 of 2 member(s) ready bus_test.go:147: bundle: [mesh-delivery] a composed check of feat/x (check-1) that is not the one asked: history bus_test.go:551: within 10s: the operator to be asked once for the group did not happen FAIL mesh-delivery/cmd/mesh-delivery 20.879s ```
jschoubben added 1 commit 2026-10-18 10:34:04 +00:00
mesh-delivery bus test waits for the group's composed check, not a member's own check asked at once (issue 1115)
mesh/merge-gate head 695446729264 merged into trunk 580fadb63ecb — pass: builds mesh-delivery → novox; no bus step; every machine composes with the change …
Details
mesh/repo-check head 695446729264 merged into trunk 580fadb63ecb — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
Details
mesh/delivery delivered
Details
6954467292
mesh-tools commented 2026-10-18 10:37:25 +00:00
Author
Member
Copy Link
Copy Source

Merge check at 69544672
Judged: head 695446729264 merged into trunk 580fadb63ecb; read beside it: mesh-controller 54070f5bc32b, mesh-controller-main 54070f5bc32b, mesh-host 6469e8238443, mesh-tools 7412c5b6c9c5

  • 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/bus_test.go, modules/mesh-delivery/cmd/mesh-delivery/checkask_test.go, modules/mesh-delivery/cmd/mesh-delivery/fakes_test.go, modules/mesh-delivery/cmd/mesh-delivery/group_test.go, modules/mesh-delivery/cmd/mesh-delivery/holder_test.go, modules/mesh-delivery/cmd/mesh-delivery/pullkey_test.go, modules/mesh-delivery/cmd/mesh-delivery/ready_test.go, modules/mesh-delivery/cmd/mesh-delivery/timers_test.go, modules/mesh-delivery/cmd/mesh-delivery/unchecked_events_test.go

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

--- the gate: mesh-delivery
note: mesh-delivery uses the seat "operator-channel", which no module declares and the mesh does not define among the manifests given; registration judges it against the whole catalogue, and passing the declaring module's manifest too judges it here
mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-backups-again, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, seat:mesh-controller.forget-checks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, gitea.gitea_open_pulls, gitea.gitea_merge_pull_request, gitea.gitea_add_comment, seat:operator-channel.notify, keeps state deliveries, groups, asked, pulls
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-18T10:07:06Z says they run
composing every machine as the mesh is
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
composing every machine with the change
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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
HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
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-18T10:07:06Z

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-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, 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/bus_test.go, modules/mesh-delivery/cmd/mesh-delivery/checkask_test.go, modules/mesh-delivery/cmd/mesh-delivery/fakes_test.go, modules/mesh-delivery/cmd/mesh-delivery/group_test.go, modules/mesh-delivery/cmd/mesh-delivery/holder_test.go, modules/mesh-delivery/cmd/mesh-delivery/pullkey_test.go, modules/mesh-delivery/cmd/mesh-delivery/ready_test.go, modules/mesh-delivery/cmd/mesh-delivery/timers_test.go and modules/mesh-delivery/cmd/mesh-delivery/unchecked_events_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 53793 strings of 807 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.013s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/mailstore	0.009s
mail-store: claimed only by mesh-mail
ok  	git.novox.be/novox/mesh-catalog/checks/sshdir	0.018s
~/.ssh: named only by ssh-client
ok  	git.novox.be/novox/mesh-catalog/checks/owned	0.008s
owned paths: every directory and archive says how it treats unknown files; no module declares inside another's directory
ok  	git.novox.be/novox/mesh-catalog/checks/secrets	0.014s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
ok  	git.novox.be/novox/mesh-catalog/checks/predefined	0.270s
predefined.json: 2 key(s), none removed that a module names
ok  	git.novox.be/novox/mesh-catalog/checks/config	0.015s
config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved)
ok  	git.novox.be/novox/mesh-catalog/checks/templates	0.012s
templates: no module keeps a file's text inline but the 0 listed
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: 61, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.232s
testing modules/mesh-delivery
ok  	mesh-delivery/cmd/mesh-delivery	12.413s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `69544672` Judged: head `695446729264` merged into trunk `580fadb63ecb`; read beside it: mesh-controller `54070f5bc32b`, mesh-controller-main `54070f5bc32b`, mesh-host `6469e8238443`, mesh-tools `7412c5b6c9c5` - `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/bus_test.go, modules/mesh-delivery/cmd/mesh-delivery/checkask_test.go, modules/mesh-delivery/cmd/mesh-delivery/fakes_test.go, modules/mesh-delivery/cmd/mesh-delivery/group_test.go, modules/mesh-delivery/cmd/mesh-delivery/holder_test.go, modules/mesh-delivery/cmd/mesh-delivery/pullkey_test.go, modules/mesh-delivery/cmd/mesh-delivery/ready_test.go, modules/mesh-delivery/cmd/mesh-delivery/timers_test.go, modules/mesh-delivery/cmd/mesh-delivery/unchecked_events_test.go Run by the build seat on shanks as `build-1792319647858778770` (`builds --log build-1792319647858778770`). ``` --- the gate: mesh-delivery note: mesh-delivery uses the seat "operator-channel", which no module declares and the mesh does not define among the manifests given; registration judges it against the whole catalogue, and passing the declaring module's manifest too judges it here mesh-delivery: ok, 1 tool(s), invokes seat:mesh-controller.delivery-plan, seat:mesh-controller.delivery-check, seat:mesh-controller.deliver, seat:mesh-controller.delivery-backups-again, seat:mesh-controller.delivery-stop, seat:mesh-controller.delivery-walks, seat:mesh-controller.forget-checks, gitea.gitea_note_append, gitea.gitea_delivery_view, gitea.gitea_commit_status, gitea.gitea_commit_statuses, gitea.gitea_contains, gitea.gitea_open_pulls, gitea.gitea_merge_pull_request, gitea.gitea_add_comment, seat:operator-channel.notify, keeps state deliveries, groups, asked, pulls 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-18T10:07:06Z says they run composing every machine as the mesh is HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus composing every machine with the change HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on f35; sealed by the controller until the vault holds it: mesh-provisioner-client — own/f35/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on idt; sealed by the controller until the vault holds it: mesh-provisioner-client — own/idt/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus HELD: the vault did not answer for the core's credentials on ygcyr; sealed by the controller until the vault holds it: mesh-provisioner, mesh-provisioner-client, nats — own/ygcyr/mesh-provisioner/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus; own/ygcyr/nats/broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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 HELD: the vault did not answer for the core's credentials on yvbpsm; sealed by the controller until the vault holds it: mesh-provisioner-client — own/yvbpsm/mesh-provisioner-client/provisioner-broker: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus 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-18T10:07:06Z 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-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, 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/bus_test.go, modules/mesh-delivery/cmd/mesh-delivery/checkask_test.go, modules/mesh-delivery/cmd/mesh-delivery/fakes_test.go, modules/mesh-delivery/cmd/mesh-delivery/group_test.go, modules/mesh-delivery/cmd/mesh-delivery/holder_test.go, modules/mesh-delivery/cmd/mesh-delivery/pullkey_test.go, modules/mesh-delivery/cmd/mesh-delivery/ready_test.go, modules/mesh-delivery/cmd/mesh-delivery/timers_test.go and modules/mesh-delivery/cmd/mesh-delivery/unchecked_events_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 53793 strings of 807 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/mailstore 0.009s mail-store: claimed only by mesh-mail ok git.novox.be/novox/mesh-catalog/checks/sshdir 0.018s ~/.ssh: named only by ssh-client ok git.novox.be/novox/mesh-catalog/checks/owned 0.008s owned paths: every directory and archive says how it treats unknown files; no module declares inside another's directory ok git.novox.be/novox/mesh-catalog/checks/secrets 0.014s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) ok git.novox.be/novox/mesh-catalog/checks/predefined 0.270s predefined.json: 2 key(s), none removed that a module names ok git.novox.be/novox/mesh-catalog/checks/config 0.015s config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved) ok git.novox.be/novox/mesh-catalog/checks/templates 0.012s templates: no module keeps a file's text inline but the 0 listed 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: 61, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.232s testing modules/mesh-delivery ok mesh-delivery/cmd/mesh-delivery 12.413s --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-tools merged commit 7f77ce663a into main 2026-10-18 10:38:06 +00:00
mesh-tools deleted branch fix/zero-delay 2026-10-18 10:38:06 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
mesh/ready
Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#361