The rest of the mesh resolves each machine with its pins and names what it leaves out; a built-by edge never widens a plan; plans stop #199

2026-10-01T16:22:45Z

mesh-admin commented

2026-10-01 16:22:45 +00:00

Three commits from this evening's fault (hq issue 188):

theRestOfTheMesh's second pass resolved every other machine without its pins. Under #195/#196's rule a machine with two providers of one provision is refused unless a pin names one, so the control node — pinned or not — was refused there and vanished: every seat it holds read as unheld, the builder's and proxy's builds were refused for want of the git seat's clone base, the roll-out was refused, and the first tiered plan failed at tier 0. Each machine is now resolved as its plan resolves it, with its pins. Proven against the live store with a diagnostic build: git — gitea on novox, mesh-build-machine — builder on novox, mesh-store, mesh-vault held again.
Both passes that skipped a refusing machine in silence (onTheNetwork, theRestOfTheMesh) now say which machine and the resolver's words.
A built-by edge orders and gates a plan but never widens it: the first live plan took 75 modules along for a controller change because everything is built by the builder and the builder packages the controller. Reachability follows code and build edges only; a controller merge is now the builder, then the controller and the proxy. plans stop <id> ends a plan by hand.

make check on the branch. Roll-out note: the running controller cannot build the builder (it still drops the control node), so this is built with build novox/mesh-controller --self --ref main --wait and pushed from a one-shot of the new image, as #197 was.

Three commits from this evening's fault (hq issue 188): - `theRestOfTheMesh`'s second pass resolved every other machine **without its pins**. Under #195/#196's rule a machine with two providers of one provision is refused unless a pin names one, so the control node — pinned or not — was refused there and vanished: every seat it holds read as unheld, the builder's and proxy's builds were refused for want of the git seat's clone base, the roll-out was refused, and the first tiered plan failed at tier 0. Each machine is now resolved as its plan resolves it, with its pins. Proven against the live store with a diagnostic build: `git — gitea on novox`, `mesh-build-machine — builder on novox`, `mesh-store`, `mesh-vault` held again. - Both passes that skipped a refusing machine in silence (`onTheNetwork`, `theRestOfTheMesh`) now say which machine and the resolver's words. - A `built-by` edge orders and gates a plan but never widens it: the first live plan took 75 modules along for a controller change because everything is built by the builder and the builder packages the controller. Reachability follows code and build edges only; a controller merge is now the builder, then the controller and the proxy. `plans stop <id>` ends a plan by hand. `make check` on the branch. Roll-out note: the running controller cannot build the builder (it still drops the control node), so this is built with `build novox/mesh-controller --self --ref main --wait` and pushed from a one-shot of the new image, as #197 was.

mesh-admin added 4 commits 2026-10-01 16:22:45 +00:00

A machine the network filter drops is said, not skipped in silence (hq issue 188) 884c088949

onTheNetwork resolves every machine unchecked and skipped one whose resolution refused. A machine
skipped there has no address, so its own plan fails on the first placeholder that needs one, in another
module's words, every seat held on it reads as unheld, and what is built from it cannot be built — four
symptoms, none naming the refusal (2026-10-01, the control node, forty minutes). The refusal is now said
where it happens, in the resolver's own words.

Merge remote-tracking branch 'origin/main' into fix/a-machine-not-on-the-network-is-said 882687afd4

A built-by edge orders and gates a plan; it never widens it — and plans stop d94f9e7f9f

The first live plan took seventy-five modules along for a controller change: the builder packages the
controller's source, everything is built by the builder, so everything was reachable. A module built by
the build machine is not changed by a new build machine. Reachability now follows the code and build
edges only; built-by still orders a tier after the build machine and gates it on the machine's roll-out.
plans stop <id> ends a plan by hand: what was asked still builds and registers, nothing further is asked.

The rest of the mesh resolves each machine with its own pins, and says which machine it leaves out dcf6278523

The second pass of theRestOfTheMesh resolved every machine without its pins. Since a machine with two
providers of one provision is refused unless a pin names one (195/196), the control node was refused
there and vanished: every seat it holds read as unheld, the build machine refused what needs the git
seat, the roll-out was refused — and nothing said why (hq issue 188). Each machine is now resolved as
its plan resolves it, with its pins; a machine left out is named with the resolver's words.

mesh-admin merged commit ba6a3ea829 into main

2026-10-01 16:25:09 +00:00

mesh-admin deleted branch fix/a-machine-not-on-the-network-is-said

2026-10-01 16:25:09 +00:00

mesh-admin referenced this pull request

2026-10-01 18:53:44 +00:00

The rest of the mesh is quiet about a machine it resolved without the excluded one's offers #200

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#199