novox/mesh-delivery
19
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Make the builder's build capacity a setting per node, hold a failed second-node build until the nodes change, and close keys left building for a vanished fingerprint (issues 1661, 1664, 1660) #14

Merged
mesh-tools merged 2 commits from fix/1661-builder-follow-ups into main 2026-10-21 12:26:04 +00:00
Conversation 3 Commits 2 Files Changed 15
+429 -32
mesh-tools commented 2026-10-21 11:59:36 +00:00
Member
Copy Link
Copy Source

Follow-ups of the R4c-4 builder (mesh-delivery #12), found by its review.

  • 1661: build capacity is the builder's capacity setting (config laid into settings.json through takes-config, read via MESH_BUILDER_SETTINGS, the process restarts on a change), as ADR 0478 §3 says, instead of a fixed environment line. Starting value shanks=3, ace=2, g14=0, novox=0 (the operator, 2026-10-21 13:40: the builder builds on shanks and ace only, as build-agent does today); 0 = never chosen, also left out of the second-node check; a node not named builds at 1.
  • 1664: a one-node done key whose second-node build fails is held until the nodes change (presence, health, a toolchain), not rebuilt at every modules value or Reconsider; the hold is in memory, so a restart gives one more try.
  • 1660: at start, after the modules bucket settles, Builder.Sweep closes every 'building' key of a fingerprint its module no longer has (failed by compare-and-set, 'closed at start: ...'); the current fingerprint's key is still taken over (§6).

Tests: 1664 and 1660 fail on main; capacity 0 tested in the parser, the choice, a whole build and the manifest default.
Try: build-1792583766012430882 passed (58 s) at 46702d1af3.

ADR 0478 §3's starting values (g14 and novox at 1) are changed by the operator's word; a record says so (in review).

Fixes issues 1661, 1664, 1660.

Reviewed-by: reviewer-r4c4@shanks at 46702d1af3

Follow-ups of the R4c-4 builder (mesh-delivery #12), found by its review. - 1661: build capacity is the builder's `capacity` setting (config laid into settings.json through takes-config, read via MESH_BUILDER_SETTINGS, the process restarts on a change), as ADR 0478 §3 says, instead of a fixed environment line. Starting value shanks=3, ace=2, g14=0, novox=0 (the operator, 2026-10-21 13:40: the builder builds on shanks and ace only, as build-agent does today); 0 = never chosen, also left out of the second-node check; a node not named builds at 1. - 1664: a one-node done key whose second-node build fails is held until the nodes change (presence, health, a toolchain), not rebuilt at every modules value or Reconsider; the hold is in memory, so a restart gives one more try. - 1660: at start, after the modules bucket settles, Builder.Sweep closes every 'building' key of a fingerprint its module no longer has (failed by compare-and-set, 'closed at start: ...'); the current fingerprint's key is still taken over (§6). Tests: 1664 and 1660 fail on main; capacity 0 tested in the parser, the choice, a whole build and the manifest default. Try: build-1792583766012430882 passed (58 s) at 46702d1af311a05c7a37ff90f6fee888c94b3e84. ADR 0478 §3's starting values (g14 and novox at 1) are changed by the operator's word; a record says so (in review). Fixes issues 1661, 1664, 1660. Reviewed-by: reviewer-r4c4@shanks at 46702d1af311a05c7a37ff90f6fee888c94b3e84
mesh-tools added 2 commits 2026-10-21 11:59:36 +00:00
Make the builder's capacity a module setting, hold back a failed second-node build until the nodes change, and close at start a key left building for a fingerprint the module no longer has (issues 1661, 1664, 1660) dcf62b0413
Keep the builder off a node whose capacity setting is 0, and start the setting at shanks=3,ace=2,g14=0,novox=0 (issue 1661)
mesh/merge-gate head 46702d1af311 merged into trunk 2000c841bf70 — pass: builds mesh-delivery-builder, sent nowhere; no bus step; every machine composes wi…
Details
mesh/repo-check head 46702d1af311 merged into trunk 2000c841bf70 — pass: its merge-check.sh passed
Details
mesh/delivery delivered
Details
46702d1af3
mesh-tools commented 2026-10-21 12:00:10 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/mesh-delivery@46702d1af311 — delivered since 2026-10-21T12:29:34Z

Delivery plan — builds mesh-delivery-builder, sent nowhere; no bus step

  • tier 0: mesh-delivery-builder

Machines

  • mesh-delivery-builder on every machine running it: sent

Transitions

  • 2026-10-21 11:59 (new) → proposed (announced): novox/mesh-delivery#14's head announced
  • 2026-10-21 12:22 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-21 12:22 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-21 12:26 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-21 12:26 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-21 12:29 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-delivery@46702d1af311` — **delivered** since 2026-10-21T12:29:34Z **Delivery plan** — builds mesh-delivery-builder, sent nowhere; no bus step - tier 0: mesh-delivery-builder **Machines** - mesh-delivery-builder on every machine running it: sent **Transitions** - 2026-10-21 11:59 (new) → proposed (announced): novox/mesh-delivery#14's head announced - 2026-10-21 12:22 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-21 12:22 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-21 12:26 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-21 12:26 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-21 12:29 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-21 12:10:05 +00:00
Author
Member
Copy Link
Copy Source

Merge check at 46702d1a
Judged: head 46702d1af311 merged into trunk d68d7ef3d9af; read beside it: mesh-catalog 4efac366cebb, mesh-controller 5be1cfaed19b, mesh-controller-main 5be1cfaed19b, mesh-host c5c4caa2a4ab, mesh-tools e0fadc43d9dd

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

Delivery plan — builds mesh-delivery-builder, sent nowhere; no bus step

  • tier 0: mesh-delivery-builder
  • read by no module's build: modules/mesh-delivery-builder/cmd/mesh-delivery-builder/integration_test.go, modules/mesh-delivery-builder/cmd/mesh-delivery-builder/settings_test.go, modules/mesh-delivery-builder/files/settings.json, modules/mesh-delivery-builder/internal/build/claim_test.go, modules/mesh-delivery-builder/internal/build/followups_test.go, modules/mesh-delivery-builder/internal/build/places_test.go, modules/mesh-delivery-builder/manifest_test.go

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

--- the gate: mesh-delivery-builder
mesh-delivery-builder: ok, invokes mesh-build-go.build_go_build, mesh-build-go.build_go_fetch, mesh-build-node.build_node_build, mesh-build-node.build_node_fetch, keeps state builds, reads mesh-build-go.steps, mesh-build-go.toolchains, mesh-build-node.steps, mesh-build-node.toolchains, mesh-delivery-indexer.manifests, mesh-delivery-indexer.modules, mesh-delivery-watchman.presence, node-engine.have, ready: builder by unit every 30s
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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-21T11:59:09Z 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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-21T11:59:09Z

modules the change moves:
  - mesh-delivery-builder (changed)

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-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-builder

notes:
  - modules/mesh-delivery-builder/cmd/mesh-delivery-builder/integration_test.go, modules/mesh-delivery-builder/cmd/mesh-delivery-builder/settings_test.go, modules/mesh-delivery-builder/files/settings.json, modules/mesh-delivery-builder/internal/build/claim_test.go, modules/mesh-delivery-builder/internal/build/followups_test.go, modules/mesh-delivery-builder/internal/build/places_test.go and modules/mesh-delivery-builder/manifest_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
== ./modules/mesh-delivery-builder: go vet and the unit tests
ok  	mesh-delivery-builder	0.003s
ok  	mesh-delivery-builder/cmd/mesh-delivery-builder	(cached)
ok  	mesh-delivery-builder/internal/build	(cached)
== ./modules/mesh-delivery-builder: the integration tests (-tags integration)
ok  	mesh-delivery-builder	0.004s
ok  	mesh-delivery-builder/cmd/mesh-delivery-builder	2.011s
ok  	mesh-delivery-builder/internal/build	(cached)
== ./modules/mesh-delivery-forge-bridge: go vet and the unit tests
ok  	mesh-delivery-forge-bridge	0.003s
ok  	mesh-delivery-forge-bridge/cmd/mesh-delivery-forge-bridge	(cached)
ok  	mesh-delivery-forge-bridge/internal/bridge	0.199s
== ./modules/mesh-delivery-forge-bridge: the integration tests (-tags integration)
ok  	mesh-delivery-forge-bridge	0.003s
ok  	mesh-delivery-forge-bridge/cmd/mesh-delivery-forge-bridge	3.645s
ok  	mesh-delivery-forge-bridge/internal/bridge	0.199s
== ./modules/mesh-delivery-indexer: go vet and the unit tests
ok  	mesh-delivery-indexer	0.003s
ok  	mesh-delivery-indexer/cmd/mesh-delivery-indexer	(cached)
ok  	mesh-delivery-indexer/internal/index	0.065s
== ./modules/mesh-delivery-indexer: the integration tests (-tags integration)
ok  	mesh-delivery-indexer	0.004s
ok  	mesh-delivery-indexer/cmd/mesh-delivery-indexer	0.666s
ok  	mesh-delivery-indexer/internal/index	0.045s
== ./modules/mesh-delivery-teller: go vet and the unit tests
ok  	mesh-delivery-teller	0.004s
ok  	mesh-delivery-teller/cmd/mesh-delivery-teller	(cached)
== ./modules/mesh-delivery-teller: the integration tests (-tags integration)
ok  	mesh-delivery-teller	0.003s
ok  	mesh-delivery-teller/cmd/mesh-delivery-teller	(cached)
== ./modules/mesh-delivery-view: go vet and the unit tests
ok  	mesh-delivery-view	0.003s
ok  	mesh-delivery-view/cmd/mesh-delivery-cli	(cached)
ok  	mesh-delivery-view/cmd/mesh-delivery-view	(cached)
ok  	mesh-delivery-view/internal/view	(cached)
== ./modules/mesh-delivery-view: the integration tests (-tags integration)
ok  	mesh-delivery-view	0.004s
ok  	mesh-delivery-view/cmd/mesh-delivery-cli	(cached)
ok  	mesh-delivery-view/cmd/mesh-delivery-view	(cached)
ok  	mesh-delivery-view/internal/view	(cached)
== ./modules/mesh-delivery-watchman: go vet and the unit tests
ok  	mesh-delivery-watchman	0.003s
ok  	mesh-delivery-watchman/cmd/mesh-delivery-watchman	(cached)
ok  	mesh-delivery-watchman/internal/watch	(cached)
== ./modules/mesh-delivery-watchman: the integration tests (-tags integration)
ok  	mesh-delivery-watchman	0.004s
ok  	mesh-delivery-watchman/cmd/mesh-delivery-watchman	(cached)
ok  	mesh-delivery-watchman/internal/watch	(cached)

Out of date when it landed: out of date: judged against trunk d68d7ef3d9, the trunk is now 2000c841bf70; judged again on a recheck or when it is merged

**Merge check** at `46702d1a` Judged: head `46702d1af311` merged into trunk `d68d7ef3d9af`; read beside it: mesh-catalog `4efac366cebb`, mesh-controller `5be1cfaed19b`, mesh-controller-main `5be1cfaed19b`, mesh-host `c5c4caa2a4ab`, mesh-tools `e0fadc43d9dd` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-delivery-builder) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds mesh-delivery-builder, sent nowhere; no bus step - tier 0: mesh-delivery-builder - read by no module's build: modules/mesh-delivery-builder/cmd/mesh-delivery-builder/integration_test.go, modules/mesh-delivery-builder/cmd/mesh-delivery-builder/settings_test.go, modules/mesh-delivery-builder/files/settings.json, modules/mesh-delivery-builder/internal/build/claim_test.go, modules/mesh-delivery-builder/internal/build/followups_test.go, modules/mesh-delivery-builder/internal/build/places_test.go, modules/mesh-delivery-builder/manifest_test.go Run by the build seat on shanks as `build-1792584006356741063` (`builds --log build-1792584006356741063`). ``` --- the gate: mesh-delivery-builder mesh-delivery-builder: ok, invokes mesh-build-go.build_go_build, mesh-build-go.build_go_fetch, mesh-build-node.build_node_build, mesh-build-node.build_node_fetch, keeps state builds, reads mesh-build-go.steps, mesh-build-go.toolchains, mesh-build-node.steps, mesh-build-node.toolchains, mesh-delivery-indexer.manifests, mesh-delivery-indexer.modules, mesh-delivery-watchman.presence, node-engine.have, ready: builder by unit every 30s 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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-21T11:59:09Z 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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-21T11:59:09Z modules the change moves: - mesh-delivery-builder (changed) machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-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-builder notes: - modules/mesh-delivery-builder/cmd/mesh-delivery-builder/integration_test.go, modules/mesh-delivery-builder/cmd/mesh-delivery-builder/settings_test.go, modules/mesh-delivery-builder/files/settings.json, modules/mesh-delivery-builder/internal/build/claim_test.go, modules/mesh-delivery-builder/internal/build/followups_test.go, modules/mesh-delivery-builder/internal/build/places_test.go and modules/mesh-delivery-builder/manifest_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) == ./modules/mesh-delivery-builder: go vet and the unit tests ok mesh-delivery-builder 0.003s ok mesh-delivery-builder/cmd/mesh-delivery-builder (cached) ok mesh-delivery-builder/internal/build (cached) == ./modules/mesh-delivery-builder: the integration tests (-tags integration) ok mesh-delivery-builder 0.004s ok mesh-delivery-builder/cmd/mesh-delivery-builder 2.011s ok mesh-delivery-builder/internal/build (cached) == ./modules/mesh-delivery-forge-bridge: go vet and the unit tests ok mesh-delivery-forge-bridge 0.003s ok mesh-delivery-forge-bridge/cmd/mesh-delivery-forge-bridge (cached) ok mesh-delivery-forge-bridge/internal/bridge 0.199s == ./modules/mesh-delivery-forge-bridge: the integration tests (-tags integration) ok mesh-delivery-forge-bridge 0.003s ok mesh-delivery-forge-bridge/cmd/mesh-delivery-forge-bridge 3.645s ok mesh-delivery-forge-bridge/internal/bridge 0.199s == ./modules/mesh-delivery-indexer: go vet and the unit tests ok mesh-delivery-indexer 0.003s ok mesh-delivery-indexer/cmd/mesh-delivery-indexer (cached) ok mesh-delivery-indexer/internal/index 0.065s == ./modules/mesh-delivery-indexer: the integration tests (-tags integration) ok mesh-delivery-indexer 0.004s ok mesh-delivery-indexer/cmd/mesh-delivery-indexer 0.666s ok mesh-delivery-indexer/internal/index 0.045s == ./modules/mesh-delivery-teller: go vet and the unit tests ok mesh-delivery-teller 0.004s ok mesh-delivery-teller/cmd/mesh-delivery-teller (cached) == ./modules/mesh-delivery-teller: the integration tests (-tags integration) ok mesh-delivery-teller 0.003s ok mesh-delivery-teller/cmd/mesh-delivery-teller (cached) == ./modules/mesh-delivery-view: go vet and the unit tests ok mesh-delivery-view 0.003s ok mesh-delivery-view/cmd/mesh-delivery-cli (cached) ok mesh-delivery-view/cmd/mesh-delivery-view (cached) ok mesh-delivery-view/internal/view (cached) == ./modules/mesh-delivery-view: the integration tests (-tags integration) ok mesh-delivery-view 0.004s ok mesh-delivery-view/cmd/mesh-delivery-cli (cached) ok mesh-delivery-view/cmd/mesh-delivery-view (cached) ok mesh-delivery-view/internal/view (cached) == ./modules/mesh-delivery-watchman: go vet and the unit tests ok mesh-delivery-watchman 0.003s ok mesh-delivery-watchman/cmd/mesh-delivery-watchman (cached) ok mesh-delivery-watchman/internal/watch (cached) == ./modules/mesh-delivery-watchman: the integration tests (-tags integration) ok mesh-delivery-watchman 0.004s ok mesh-delivery-watchman/cmd/mesh-delivery-watchman (cached) ok mesh-delivery-watchman/internal/watch (cached) ``` **Out of date when it landed**: out of date: judged against trunk d68d7ef3d9af, the trunk is now 2000c841bf70; judged again on a recheck or when it is merged
mesh-tools commented 2026-10-21 12:22:46 +00:00
Author
Member
Copy Link
Copy Source

Merge check at 46702d1a
Judged: head 46702d1af311 merged into trunk 2000c841bf70; read beside it: mesh-catalog 4efac366cebb, mesh-controller 5be1cfaed19b, mesh-controller-main 5be1cfaed19b, mesh-host c5c4caa2a4ab, mesh-tools e0fadc43d9dd

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

Delivery plan — builds mesh-delivery-builder, sent nowhere; no bus step

  • tier 0: mesh-delivery-builder
  • read by no module's build: modules/mesh-delivery-builder/cmd/mesh-delivery-builder/integration_test.go, modules/mesh-delivery-builder/cmd/mesh-delivery-builder/settings_test.go, modules/mesh-delivery-builder/files/settings.json, modules/mesh-delivery-builder/internal/build/claim_test.go, modules/mesh-delivery-builder/internal/build/followups_test.go, modules/mesh-delivery-builder/internal/build/places_test.go, modules/mesh-delivery-builder/manifest_test.go

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

--- the gate: mesh-delivery-builder
mesh-delivery-builder: ok, invokes mesh-build-go.build_go_build, mesh-build-go.build_go_fetch, mesh-build-node.build_node_build, mesh-build-node.build_node_fetch, keeps state builds, reads mesh-build-go.steps, mesh-build-go.toolchains, mesh-build-node.steps, mesh-build-node.toolchains, mesh-delivery-indexer.manifests, mesh-delivery-indexer.modules, mesh-delivery-watchman.presence, node-engine.have, ready: builder by unit every 30s
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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-21T12:08:09Z 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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-21T12:08:09Z

modules the change moves:
  - mesh-delivery-builder (changed)

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-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-builder

notes:
  - modules/mesh-delivery-builder/cmd/mesh-delivery-builder/integration_test.go, modules/mesh-delivery-builder/cmd/mesh-delivery-builder/settings_test.go, modules/mesh-delivery-builder/files/settings.json, modules/mesh-delivery-builder/internal/build/claim_test.go, modules/mesh-delivery-builder/internal/build/followups_test.go, modules/mesh-delivery-builder/internal/build/places_test.go and modules/mesh-delivery-builder/manifest_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
== ./modules/mesh-delivery-builder: go vet and the unit tests
ok  	mesh-delivery-builder	0.004s
ok  	mesh-delivery-builder/cmd/mesh-delivery-builder	(cached)
ok  	mesh-delivery-builder/internal/build	(cached)
== ./modules/mesh-delivery-builder: the integration tests (-tags integration)
ok  	mesh-delivery-builder	0.003s
ok  	mesh-delivery-builder/cmd/mesh-delivery-builder	2.015s
ok  	mesh-delivery-builder/internal/build	(cached)
== ./modules/mesh-delivery-forge-bridge: go vet and the unit tests
ok  	mesh-delivery-forge-bridge	0.003s
ok  	mesh-delivery-forge-bridge/cmd/mesh-delivery-forge-bridge	(cached)
ok  	mesh-delivery-forge-bridge/internal/bridge	0.198s
== ./modules/mesh-delivery-forge-bridge: the integration tests (-tags integration)
ok  	mesh-delivery-forge-bridge	0.003s
ok  	mesh-delivery-forge-bridge/cmd/mesh-delivery-forge-bridge	3.576s
ok  	mesh-delivery-forge-bridge/internal/bridge	0.199s
== ./modules/mesh-delivery-indexer: go vet and the unit tests
ok  	mesh-delivery-indexer	0.003s
ok  	mesh-delivery-indexer/cmd/mesh-delivery-indexer	(cached)
ok  	mesh-delivery-indexer/internal/index	0.038s
== ./modules/mesh-delivery-indexer: the integration tests (-tags integration)
ok  	mesh-delivery-indexer	0.004s
ok  	mesh-delivery-indexer/cmd/mesh-delivery-indexer	0.638s
ok  	mesh-delivery-indexer/internal/index	0.039s
== ./modules/mesh-delivery-teller: go vet and the unit tests
ok  	mesh-delivery-teller	0.003s
ok  	mesh-delivery-teller/cmd/mesh-delivery-teller	(cached)
== ./modules/mesh-delivery-teller: the integration tests (-tags integration)
ok  	mesh-delivery-teller	0.003s
ok  	mesh-delivery-teller/cmd/mesh-delivery-teller	(cached)
== ./modules/mesh-delivery-view: go vet and the unit tests
ok  	mesh-delivery-view	0.003s
ok  	mesh-delivery-view/cmd/mesh-delivery-cli	(cached)
ok  	mesh-delivery-view/cmd/mesh-delivery-view	(cached)
ok  	mesh-delivery-view/cmd/mesh-delivery-view-tools	(cached)
ok  	mesh-delivery-view/internal/view	(cached)
== ./modules/mesh-delivery-view: the integration tests (-tags integration)
ok  	mesh-delivery-view	0.003s
ok  	mesh-delivery-view/cmd/mesh-delivery-cli	(cached)
ok  	mesh-delivery-view/cmd/mesh-delivery-view	(cached)
ok  	mesh-delivery-view/cmd/mesh-delivery-view-tools	(cached)
ok  	mesh-delivery-view/internal/view	(cached)
== ./modules/mesh-delivery-watchman: go vet and the unit tests
ok  	mesh-delivery-watchman	0.003s
ok  	mesh-delivery-watchman/cmd/mesh-delivery-watchman	(cached)
ok  	mesh-delivery-watchman/internal/watch	(cached)
== ./modules/mesh-delivery-watchman: the integration tests (-tags integration)
ok  	mesh-delivery-watchman	0.003s
ok  	mesh-delivery-watchman/cmd/mesh-delivery-watchman	(cached)
ok  	mesh-delivery-watchman/internal/watch	(cached)
**Merge check** at `46702d1a` Judged: head `46702d1af311` merged into trunk `2000c841bf70`; read beside it: mesh-catalog `4efac366cebb`, mesh-controller `5be1cfaed19b`, mesh-controller-main `5be1cfaed19b`, mesh-host `c5c4caa2a4ab`, mesh-tools `e0fadc43d9dd` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-delivery-builder) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds mesh-delivery-builder, sent nowhere; no bus step - tier 0: mesh-delivery-builder - read by no module's build: modules/mesh-delivery-builder/cmd/mesh-delivery-builder/integration_test.go, modules/mesh-delivery-builder/cmd/mesh-delivery-builder/settings_test.go, modules/mesh-delivery-builder/files/settings.json, modules/mesh-delivery-builder/internal/build/claim_test.go, modules/mesh-delivery-builder/internal/build/followups_test.go, modules/mesh-delivery-builder/internal/build/places_test.go, modules/mesh-delivery-builder/manifest_test.go Run by the build seat on shanks as `build-1792584609505817796` (`builds --log build-1792584609505817796`). ``` --- the gate: mesh-delivery-builder mesh-delivery-builder: ok, invokes mesh-build-go.build_go_build, mesh-build-go.build_go_fetch, mesh-build-node.build_node_build, mesh-build-node.build_node_fetch, keeps state builds, reads mesh-build-go.steps, mesh-build-go.toolchains, mesh-build-node.steps, mesh-build-node.toolchains, mesh-delivery-indexer.manifests, mesh-delivery-indexer.modules, mesh-delivery-watchman.presence, node-engine.have, ready: builder by unit every 30s 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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-21T12:08:09Z 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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 7 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, ygcyr.mesh-mail.send, node.yvbpsm, yvbpsm.brother.device. 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-21T12:08:09Z modules the change moves: - mesh-delivery-builder (changed) machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-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-builder notes: - modules/mesh-delivery-builder/cmd/mesh-delivery-builder/integration_test.go, modules/mesh-delivery-builder/cmd/mesh-delivery-builder/settings_test.go, modules/mesh-delivery-builder/files/settings.json, modules/mesh-delivery-builder/internal/build/claim_test.go, modules/mesh-delivery-builder/internal/build/followups_test.go, modules/mesh-delivery-builder/internal/build/places_test.go and modules/mesh-delivery-builder/manifest_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) == ./modules/mesh-delivery-builder: go vet and the unit tests ok mesh-delivery-builder 0.004s ok mesh-delivery-builder/cmd/mesh-delivery-builder (cached) ok mesh-delivery-builder/internal/build (cached) == ./modules/mesh-delivery-builder: the integration tests (-tags integration) ok mesh-delivery-builder 0.003s ok mesh-delivery-builder/cmd/mesh-delivery-builder 2.015s ok mesh-delivery-builder/internal/build (cached) == ./modules/mesh-delivery-forge-bridge: go vet and the unit tests ok mesh-delivery-forge-bridge 0.003s ok mesh-delivery-forge-bridge/cmd/mesh-delivery-forge-bridge (cached) ok mesh-delivery-forge-bridge/internal/bridge 0.198s == ./modules/mesh-delivery-forge-bridge: the integration tests (-tags integration) ok mesh-delivery-forge-bridge 0.003s ok mesh-delivery-forge-bridge/cmd/mesh-delivery-forge-bridge 3.576s ok mesh-delivery-forge-bridge/internal/bridge 0.199s == ./modules/mesh-delivery-indexer: go vet and the unit tests ok mesh-delivery-indexer 0.003s ok mesh-delivery-indexer/cmd/mesh-delivery-indexer (cached) ok mesh-delivery-indexer/internal/index 0.038s == ./modules/mesh-delivery-indexer: the integration tests (-tags integration) ok mesh-delivery-indexer 0.004s ok mesh-delivery-indexer/cmd/mesh-delivery-indexer 0.638s ok mesh-delivery-indexer/internal/index 0.039s == ./modules/mesh-delivery-teller: go vet and the unit tests ok mesh-delivery-teller 0.003s ok mesh-delivery-teller/cmd/mesh-delivery-teller (cached) == ./modules/mesh-delivery-teller: the integration tests (-tags integration) ok mesh-delivery-teller 0.003s ok mesh-delivery-teller/cmd/mesh-delivery-teller (cached) == ./modules/mesh-delivery-view: go vet and the unit tests ok mesh-delivery-view 0.003s ok mesh-delivery-view/cmd/mesh-delivery-cli (cached) ok mesh-delivery-view/cmd/mesh-delivery-view (cached) ok mesh-delivery-view/cmd/mesh-delivery-view-tools (cached) ok mesh-delivery-view/internal/view (cached) == ./modules/mesh-delivery-view: the integration tests (-tags integration) ok mesh-delivery-view 0.003s ok mesh-delivery-view/cmd/mesh-delivery-cli (cached) ok mesh-delivery-view/cmd/mesh-delivery-view (cached) ok mesh-delivery-view/cmd/mesh-delivery-view-tools (cached) ok mesh-delivery-view/internal/view (cached) == ./modules/mesh-delivery-watchman: go vet and the unit tests ok mesh-delivery-watchman 0.003s ok mesh-delivery-watchman/cmd/mesh-delivery-watchman (cached) ok mesh-delivery-watchman/internal/watch (cached) == ./modules/mesh-delivery-watchman: the integration tests (-tags integration) ok mesh-delivery-watchman 0.003s ok mesh-delivery-watchman/cmd/mesh-delivery-watchman (cached) ok mesh-delivery-watchman/internal/watch (cached) ```
mesh-tools merged commit b04ee76473 into main 2026-10-21 12:26:04 +00:00
mesh-tools deleted branch fix/1661-builder-follow-ups 2026-10-21 12:26:04 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-delivery#14