Issue 266: a merge on the bus was never handed to the controller #123

2026-10-05T23:30:28Z

mesh-admin commented

2026-10-05 23:30:28 +00:00

New issue, status located. It covers the symptom, the evidence (stream holds the announcement; consumer past it with nothing pending; 24 deliveries for 25 messages; 23 unmatched merges in 3 days), the cause (nats 2.10.29 multi-filter consumers skip messages, reproduced), the two fixes (mesh-catalog nats 2.11.17; mesh-controller catch-up of missed merges) and how each is checked. fixed-by is left empty until the code PRs merge.

Checks: records.py, index.py, cycle.py all pass.

New issue, status located. It covers the symptom, the evidence (stream holds the announcement; consumer past it with nothing pending; 24 deliveries for 25 messages; 23 unmatched merges in 3 days), the cause (nats 2.10.29 multi-filter consumers skip messages, reproduced), the two fixes (mesh-catalog nats 2.11.17; mesh-controller catch-up of missed merges) and how each is checked. `fixed-by` is left empty until the code PRs merge. Checks: records.py, index.py, cycle.py all pass.

mesh-admin added 1 commit 2026-10-05 23:30:28 +00:00

Issue 266: a merge on the bus was never handed to the controller 14dabf60ee

The bus server's multi-filter consumers skip messages on 2.10; record the
evidence, the reproduction, and the two fixes (server upgrade, catch-up).

mesh-admin merged commit 3ba75a312b into main

2026-10-05 23:33:20 +00:00

mesh-admin deleted branch issues/266-a-merge-the-bus-never-handed-the-controller

2026-10-05 23:33:20 +00:00

mesh-admin commented

2026-10-06 23:07:08 +00:00

Delivery novox/hq@3ba75a312b11 — held since 2026-10-06T23:05:28Z

Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/hq#123 merged; its head was not heard by this owner, so it is made from the forge's word
2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/hq@3ba75a312b11` — **held** since 2026-10-06T23:05:28Z Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on. **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/hq#123 merged; its head was not heard by this owner, so it is made from the forge's word - 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#123