Take the placement files out again: since the seed no delivery reaches any node (issue 1126, revert of #525) #527

2026-10-27T22:47:59Z

mesh-tools commented

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

Revert of #525 (the placement seed, merged 22:02:41Z). Replaces #526, which mesh-delivery kept as closed after it was reopened.

Why. No node agent switched to composing its own modules: each read its placement at its last start (21:35-21:37Z) while the bus still refused that read, and on a read error it took the controller's compositions (the fault mesh-host #154 fixes). Since the seed, the assigner writes self wants (no composition digest), so agents on the controller's compositions apply nothing ('its want names ; nothing is applied until they agree'). No delivery reaches any node, including mesh-host #154 (199f6b4) and its rollout.

What this does. Deletes placement/{ace,g14,novox,shanks}.json. The nodes already run the controller's compositions, so nothing on them changes; the assigner returns to wants naming the controller's digests and deliveries flow again.

Its check fails falsely: every engine still runs the old shadow (before 199f6b4), which answers a deleted placement as 'everything removed'. That is the fault #154 fixes; nothing is removed here.

The seed comes back once 199f6b4 runs on all four nodes and its shadow answers 'same'.

Reviewed-by: lead-47@shanks at 83e9ce5b19

Revert of #525 (the placement seed, merged 22:02:41Z). Replaces #526, which mesh-delivery kept as closed after it was reopened. **Why.** No node agent switched to composing its own modules: each read its placement at its last start (21:35-21:37Z) while the bus still refused that read, and on a read error it took the controller's compositions (the fault mesh-host #154 fixes). Since the seed, the assigner writes self wants (no composition digest), so agents on the controller's compositions apply nothing ('its want names ; nothing is applied until they agree'). No delivery reaches any node, including mesh-host #154 (199f6b4) and its rollout. **What this does.** Deletes placement/{ace,g14,novox,shanks}.json. The nodes already run the controller's compositions, so nothing on them changes; the assigner returns to wants naming the controller's digests and deliveries flow again. **Its check fails falsely:** every engine still runs the old shadow (before 199f6b4), which answers a deleted placement as 'everything removed'. That is the fault #154 fixes; nothing is removed here. The seed comes back once 199f6b4 runs on all four nodes and its shadow answers 'same'. Reviewed-by: lead-47@shanks at 83e9ce5b1957081e4e0544e9ffce71ce3ea0172f

mesh-tools added 1 commit 2026-10-27 22:47:59 +00:00

Take the placement files out again: since the seed no delivery reaches any node, because every node agent runs the controller's compositions while the wants ask them to compose their own (issue 1126, revert of #525 )

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

Details

mesh/check checking 83e9ce5b1957 on d7e8a8824e9c

83e9ce5b19

mesh-tools commented

2026-10-27 22:48:06 +00:00

Delivery novox/mesh-catalog@83e9ce5b1957 — merged since 2026-10-27T22:48:48Z

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

Transitions

2026-10-27 22:48 (new) → proposed (announced): novox/mesh-catalog#527's head announced
2026-10-27 22:48 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:48 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@83e9ce5b1957` — **merged** since 2026-10-27T22:48:48Z **Source** — source.main moved to novox/mesh-catalog@d7e8a8824e9c. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-10-27 22:48 (new) → proposed (announced): novox/mesh-catalog#527's head announced - 2026-10-27 22:48 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:48 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 d7e8a8824e into main

2026-10-27 22:48:46 +00:00

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

2026-10-27 22:48:47 +00:00

mesh-tools referenced this pull request

2026-10-27 22:52:45 +00:00

Seed the placement files a third time (issue 1126) — Approve ONLY after the lead says all four nodes answer 'same' #528

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#527