Revert L3: its node-engine removed every held module on novox, the bus server among them (issue 774) #557

2026-10-29T08:43:44Z

mesh-tools commented

2026-10-29 08:43:44 +00:00

Why

L3 (issue 774) was merged at 07:44 UTC on 2026-10-29. Its node-engine build no longer reads the kept declaration. On novox at 07:54:25 UTC that engine composed its own modules, marked nine as held (nats, route-proxy, photos, de-spiegel, link2pay among them, most because they run at an old form with no build here), and then removed every held module that had no build of its own: the bus server mesh-broker-nats and its configuration, route-proxy, the photo sites and their server, de-spiegel and link2pay. The whole mesh was off the bus from 07:54:34 to 08:38:53 UTC, when the operator recreated the bus server by hand from novox's kept declaration (its data was intact). A pin back to the pre-L3 engine cannot hold while the delivery wants L3's engine build, so the engines on ace, g14 and novox are stopped and shanks's stands aside.

Separately, L3's mesh-grants and the new engine subjects asked for grants the accounts file does not hold, so the bus refused them from 07:50 UTC.

What changes

This group reverts L3's three merges that run on machines, each to exactly its main before L3 (the tree equals the merge's first parent): mesh-host #168, mesh-delivery #105, mesh-catalog #556. The gate fix that rode in mesh-catalog #556 (answer per ask) is reverted with it and comes back with L3. hq #495 stays: it is playbook text and reaches no machine.

Quick fix or thorough fix

Quick, chosen by the operator: revert to the state that ran all night, so every engine runs the pre-L3 code again and novox's engine can put the removed modules back from its kept declaration.
Thorough, next: L3 lands again with a held module never removed (a module whose have names a composition the bucket no longer keeps is kept as it runs, never composed as nothing), and grants that cover L3's new subjects, each with a test that fails on today's code.

How it is checked

Each member's tree equals its main before L3; those trees passed their checks when merged.
Live: after the delivery every engine runs the reverted build, no "removed" line follows in any engine journal, route-proxy and the photo sites answer again on novox, and the bus refuses nothing it granted before 07:50 UTC.

Group: delivery group revert/774-l3 (mesh-host, mesh-delivery, mesh-catalog).

Reviewed-by: rev-revert@shanks at c8240c38bb

## Why L3 (issue 774) was merged at 07:44 UTC on 2026-10-29. Its node-engine build no longer reads the kept declaration. On novox at 07:54:25 UTC that engine composed its own modules, marked nine as held (nats, route-proxy, photos, de-spiegel, link2pay among them, most because they run at an old form with no build here), and then removed every held module that had no build of its own: the bus server `mesh-broker-nats` and its configuration, route-proxy, the photo sites and their server, de-spiegel and link2pay. The whole mesh was off the bus from 07:54:34 to 08:38:53 UTC, when the operator recreated the bus server by hand from novox's kept declaration (its data was intact). A pin back to the pre-L3 engine cannot hold while the delivery wants L3's engine build, so the engines on ace, g14 and novox are stopped and shanks's stands aside. Separately, L3's mesh-grants and the new engine subjects asked for grants the accounts file does not hold, so the bus refused them from 07:50 UTC. ## What changes This group reverts L3's three merges that run on machines, each to exactly its main before L3 (the tree equals the merge's first parent): mesh-host #168, mesh-delivery #105, mesh-catalog #556. The gate fix that rode in mesh-catalog #556 (answer per ask) is reverted with it and comes back with L3. hq #495 stays: it is playbook text and reaches no machine. ## Quick fix or thorough fix - Quick, chosen by the operator: revert to the state that ran all night, so every engine runs the pre-L3 code again and novox's engine can put the removed modules back from its kept declaration. - Thorough, next: L3 lands again with a held module never removed (a module whose have names a composition the bucket no longer keeps is kept as it runs, never composed as nothing), and grants that cover L3's new subjects, each with a test that fails on today's code. ## How it is checked - Each member's tree equals its main before L3; those trees passed their checks when merged. - Live: after the delivery every engine runs the reverted build, no "removed" line follows in any engine journal, route-proxy and the photo sites answer again on novox, and the bus refuses nothing it granted before 07:50 UTC. Group: delivery group revert/774-l3 (mesh-host, mesh-delivery, mesh-catalog). Reviewed-by: rev-revert@shanks at c8240c38bb8980b2540654c7838afacd7a868723

mesh-tools added 1 commit 2026-10-29 08:43:44 +00:00

Revert L3 (mesh-catalog, merge 15552413): its node-engine removed every held module on novox, the bus server among them, at 08:54 CET on 2026-10-29 (issue 774)

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

Details

mesh/delivery-group group revert/774-l3 merged: every member is merged

Details

mesh/check being carried to c8240c38bb89 on 030f9ee4e780 | from 1555241393fe | novox/mesh-catalog#557 in group revert/774-l3

c8240c38bb

L3 lands again with two fixes: a held module is never removed, and the grants cover L3's new subjects.

mesh-tools commented

2026-10-29 08:43:49 +00:00

Delivery novox/mesh-catalog@c8240c38bb89 — merged since 2026-10-29T08:59:57Z

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

Group revert/774-l3: novox/mesh-catalog@c8240c38bb, novox/mesh-delivery@6771db22ae, novox/mesh-host@f81e6147ae

composed together: pass — the checker's verdict at the members' heads (4a819c533d2e)

Transitions

2026-10-29 08:43 (new) → proposed (announced): novox/mesh-catalog#557's head announced
2026-10-29 08:43 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-29 08: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@c8240c38bb89` — **merged** since 2026-10-29T08:59:57Z **Source** — source.main moved to novox/mesh-catalog@030f9ee4e780. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `revert/774-l3`: novox/mesh-catalog@c8240c38bb89, novox/mesh-delivery@6771db22ae69, novox/mesh-host@f81e6147aee1 - composed together: pass — the checker's verdict at the members' heads (4a819c533d2e) **Transitions** - 2026-10-29 08:43 (new) → proposed (announced): novox/mesh-catalog#557's head announced - 2026-10-29 08:43 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-29 08: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 030f9ee4e7 into main

2026-10-29 08:59:53 +00:00

mesh-tools commented

2026-10-29 09:00:15 +00:00

Merged by lead-47@shanks at 08:59 UTC on the operator's approval given at the terminal on shanks at about 08:55 UTC ("Yes, if the check passes"), because the Telegram channel could not carry the Approve after the outage (messenger names no linked account; issue 774 note 41). Check mesh/check 4a819c533d2e passed at 08:57:18 for the group revert/774-l3 at the heads mesh-catalog c8240c38bb, mesh-delivery 6771db22ae69, mesh-host f81e6147aee1; the three merged in one pass.

Merged by lead-47@shanks at 08:59 UTC on the operator's approval given at the terminal on shanks at about 08:55 UTC ("Yes, if the check passes"), because the Telegram channel could not carry the Approve after the outage (messenger names no linked account; issue 774 note 41). Check mesh/check 4a819c533d2e passed at 08:57:18 for the group revert/774-l3 at the heads mesh-catalog c8240c38bb89, mesh-delivery 6771db22ae69, mesh-host f81e6147aee1; the three merged in one pass.

jschoubben referenced this issue from a commit

2026-10-29 20:16:46 +00:00

Revert "Merge pull request 'Revert L3: its node-engine removed every held module on novox, the bus server among them (issue 774)' (#557) from revert/774-l3 into main"

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#557