Take the placement files out again: every node composing its own fails (issue 1126, revert of #528) — approve now #529

2026-10-27T22:56:16Z

mesh-tools commented

2026-10-27 22:56:16 +00:00

Revert of #528 (merged 22:53:41Z).

Why. Since 22:54Z all four node agents compose their own (composes=own) and fail every module (the node keeps running what it ran):

novox, 77 modules: "nats says ${dir:mesh-state}, and nats declares no directory "mesh-state"" — a composition fault of the bus module on the node's own path; it does not heal by itself.
ace, g14, shanks, 132 modules: "frombus: the manifest of ...: the revisions of ... in mesh-delivery-indexer_manifests: nats: jetstream not enabled" — read during a two-second bus pause at 22:54:19Z and not retried since.
So no delivery reaches any node, and 209 haves read failed.

What this does. Deletes the placement files. Every node runs mesh-host 199f6b4, which on a deleted placement key ends its run and begins again on the controller's compositions without a restart (tested in H8): the compositions they ran until 22:53Z. Deliveries flow again.

Its check: the nodes' shadow now answers a deletion by comparing the controller's compositions with what runs (Returns); it may still answer 'differs' for files carried by digest vs inline.

Reviewed-by: lead-47@shanks at bd65c839a8

Revert of #528 (merged 22:53:41Z). **Why.** Since 22:54Z all four node agents compose their own (composes=own) and fail every module (the node keeps running what it ran): - novox, 77 modules: "nats says ${dir:mesh-state}, and nats declares no directory \"mesh-state\"" — a composition fault of the bus module on the node's own path; it does not heal by itself. - ace, g14, shanks, 132 modules: "frombus: the manifest of <m> ...: the revisions of ... in mesh-delivery-indexer_manifests: nats: jetstream not enabled" — read during a two-second bus pause at 22:54:19Z and not retried since. So no delivery reaches any node, and 209 haves read failed. **What this does.** Deletes the placement files. Every node runs mesh-host 199f6b4, which on a deleted placement key ends its run and begins again on the controller's compositions without a restart (tested in H8): the compositions they ran until 22:53Z. Deliveries flow again. **Its check:** the nodes' shadow now answers a deletion by comparing the controller's compositions with what runs (Returns); it may still answer 'differs' for files carried by digest vs inline. Reviewed-by: lead-47@shanks at bd65c839a881dfaa358cc7266e653e1c6e62b9dd

mesh-tools added 1 commit 2026-10-27 22:56:17 +00:00

Take the placement files out again: every node composing its own fails (novox: nats' ${dir:mesh-state} not declared; ace, g14, shanks: the build index unread at a bus pause), so each returns to the controller's compositions (issue 1126)

mesh/delivery merged: source.main moved to novox/mesh-catalog@00d155da60f5

Details

mesh/check checking bd65c839a881 on 00d155da60f5

bd65c839a8

mesh-tools commented

2026-10-27 22:56:21 +00:00

Delivery novox/mesh-catalog@bd65c839a881 — merged since 2026-10-27T22:59:39Z

Source — source.main moved to novox/mesh-catalog@00d155da60. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

2026-10-27 22:56 (new) → proposed (announced): novox/mesh-catalog#529's head announced
2026-10-27 22:56 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-10-27 22:59 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/mesh-catalog@bd65c839a881` — **merged** since 2026-10-27T22:59:39Z **Source** — source.main moved to novox/mesh-catalog@00d155da60f5. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-10-27 22:56 (new) → proposed (announced): novox/mesh-catalog#529's head announced - 2026-10-27 22:56 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-10-27 22:59 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools merged commit 00d155da60 into main

2026-10-27 22:59:37 +00:00

mesh-tools deleted branch revert/1126-seed-4

2026-10-27 22:59:37 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#529