Issue 314: a large answer was lost on its way back; issue 200 resolved by 265's fix #198

2026-10-08T09:30:17Z

mesh-admin commented

2026-10-08 09:30:17 +00:00

Issue 314 (located). The controller's conditions and status grew past the bus's max_payload once 689 stalled deliveries were open conditions. The client library refused each reply inside the controller. Every caller timed out, and calls said each call was answered. The issue covers how a verb's answer travels, the proof (R314, PROVED by the lab's prover), what was ruled out, and the fix: oversize answers are paged in the reply path and joined by the askers, and the overviews are brief. fixed-by: novox/mesh-controller #138, novox/mesh-tools #22, novox/mesh-lab #66. replay: R314.
Issue 200 resolved. Its Publish Violation was issue 265's mechanism: a broker reload forgets the reply permission. 265's fix removed it, and only one inbox violation was logged since, on 2026-10-06. 314 is a different fault: a payload over the limit never reaches the server, so it cannot produce a violation. The workstation's node name in 200's quoted log is replaced by a role name.

sh merge-check.sh: records, index, cycle and words all pass.

Merge after the three code PRs, so fixed-by names merged work. Status moves to resolved once conditions answers live through the mesh MCP server.

- **Issue 314** (located). The controller's `conditions` and `status` grew past the bus's `max_payload` once 689 stalled deliveries were open conditions. The client library refused each reply inside the controller. Every caller timed out, and `calls` said each call was answered. The issue covers how a verb's answer travels, the proof (R314, PROVED by the lab's prover), what was ruled out, and the fix: oversize answers are paged in the reply path and joined by the askers, and the overviews are brief. `fixed-by`: novox/mesh-controller #138, novox/mesh-tools #22, novox/mesh-lab #66. `replay: R314`. - **Issue 200** resolved. Its `Publish Violation` was issue 265's mechanism: a broker reload forgets the reply permission. 265's fix removed it, and only one inbox violation was logged since, on 2026-10-06. 314 is a different fault: a payload over the limit never reaches the server, so it cannot produce a violation. The workstation's node name in 200's quoted log is replaced by a role name. `sh merge-check.sh`: records, index, cycle and words all pass. Merge after the three code PRs, so `fixed-by` names merged work. Status moves to resolved once `conditions` answers live through the mesh MCP server.

mesh-admin added 1 commit 2026-10-08 09:30:17 +00:00

Issue 314: a large answer was lost on its way back; issue 200 resolved by 265's fix

mesh/merge-gate pass: the change touches no module of the mesh's graph

Details

mesh/repo-check pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

f78e21c5f9

An answer over the bus's max_payload was refused inside the controller and
every caller timed out, while calls said answered. Diagnosed and proved (R314),
and told apart from issue 200, whose permission refusal issue 265 already fixed.

mesh-admin commented

2026-10-08 09:30:24 +00:00

Delivery novox/hq@f78e21c5f9b1 — delivered since 2026-10-08T11:06:37Z

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

Transitions

2026-10-08 09:30 (new) → proposed (announced): novox/hq#198's head announced
2026-10-08 09:32 proposed → checked (checked): the verdict names this commit
2026-10-08 09:32 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 11:06 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-08 11:06 published → delivered (done): nothing for a walk to move

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

**Delivery** `novox/hq@f78e21c5f9b1` — **delivered** since 2026-10-08T11:06:37Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-08 09:30 (new) → proposed (announced): novox/hq#198's head announced - 2026-10-08 09:32 proposed → checked (checked): the verdict names this commit - 2026-10-08 09:32 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 11:06 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-08 11:06 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin merged commit df0097245d into main

2026-10-08 11:06:35 +00:00

mesh-admin deleted branch issues/314-a-large-answer-was-lost-on-its-way-back

2026-10-08 11:06:35 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#198