Join a paged answer, and say one too large instead of timing out (hq issue 314) #22

Merged
mesh-admin merged 1 commits from fix/314-a-large-answer-is-paged-not-lost into main 2026-10-08 11:06:23 +00:00
Contributor

hq issue 314. An answer over the bus's max_payload was refused by the client library inside its holder, and the caller waited out RequestTimeout (30 s) and read silence. This hit the controller's conditions and status for hours on 2026-10-08.

  • internal/bus/pages.go: when the controller answers paged (novox/mesh-controller #138), askOnce asks the same subject again with Mesh-Page: <call> <n> for each part, checks Mesh-Part, and joins the parts. A part that cannot be had, after 3 tries for a handover, fails the whole call and names the part. The answer is never shortened.
  • answerOn: a module's answer larger than one message is answered as an error that says so, at once, and the runtime logs it. A failed Respond is now logged too; it used to be ignored. Module answers are not paged, because a module's instances can share a queue group and a part could reach another instance.
  • Test: TestAnAnswerLargerThanOneMessage, run against the test bus. A paged 3 MB answer arrives whole, and an oversize module answer is refused in words within 5 s.

sh merge-check.sh: passes. internal/runtime and internal/console are not tested here, as the script says.

Independent of #138 in either order: against an old controller nothing is ever paged.

hq issue 314. An answer over the bus's `max_payload` was refused by the client library inside its holder, and the caller waited out `RequestTimeout` (30 s) and read silence. This hit the controller's `conditions` and `status` for hours on 2026-10-08. - `internal/bus/pages.go`: when the controller answers `paged` (novox/mesh-controller #138), `askOnce` asks the same subject again with `Mesh-Page: <call> <n>` for each part, checks `Mesh-Part`, and joins the parts. A part that cannot be had, after 3 tries for a handover, fails the whole call and names the part. The answer is never shortened. - `answerOn`: a module's answer larger than one message is answered as an error that says so, at once, and the runtime logs it. A failed `Respond` is now logged too; it used to be ignored. Module answers are not paged, because a module's instances can share a queue group and a part could reach another instance. - Test: `TestAnAnswerLargerThanOneMessage`, run against the test bus. A paged 3 MB answer arrives whole, and an oversize module answer is refused in words within 5 s. `sh merge-check.sh`: passes. `internal/runtime` and `internal/console` are not tested here, as the script says. Independent of #138 in either order: against an old controller nothing is ever paged.
mesh-admin added 1 commit 2026-10-08 09:29:59 +00:00
Join a paged answer, and say one too large instead of timing out (hq issue 314)
mesh/merge-gate pass: builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of …
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery delivered
mesh/delivery-group group fix/314-a-large-answer-is-paged-not-lost merged: every member is merged
90c7871276
An answer larger than the bus's max_payload was refused by the client library
inside its holder, and the caller waited out its 30 s and read silence: the
controller's conditions and status for hours on 2026-10-08. The console now asks
for the parts of an answer the controller paged and joins them; a module's answer
too large for one message is answered as an error saying so, at once.
Author
Contributor

Delivery novox/mesh-tools@90c78712767e — delivered since 2026-10-08T11:22:07Z

Delivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-tools, node-tools
  • ace: receives node-tools
  • g14: receives node-tools
  • novox: receives node-tools
  • shanks: receives node-tools
  • node-tools provides mcp-endpoint: its consumers are sent again after it

Group fix/314-a-large-answer-is-paged-not-lost, in order: novox/mesh-controller@175b28ee42 → novox/mesh-tools@90c7871276

Machines

  • mesh-tools on every machine running it: sent
  • node-tools on ace: passed — healthy 3 times over 2m52s
  • node-tools on g14: failed — carried by release-1791457717307061152
  • node-tools on novox: passed — carried by plan-1791457623441020580
  • node-tools on the rest running it: sent

Transitions

  • 2026-10-08 09:30 (new) → proposed (announced): novox/mesh-tools#22's head announced
  • 2026-10-08 09:33 proposed → checked (checked): the verdict names this commit
  • 2026-10-08 09:33 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-08 11:07 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:07 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
  • 2026-10-08 11:22 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-tools@90c78712767e` — **delivered** since 2026-10-08T11:22:07Z **Delivery plan** — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step - tier 0: mesh-tools, node-tools - ace: receives node-tools - g14: receives node-tools - novox: receives node-tools - shanks: receives node-tools - node-tools provides mcp-endpoint: its consumers are sent again after it **Group** `fix/314-a-large-answer-is-paged-not-lost`, in order: novox/mesh-controller@175b28ee421f → novox/mesh-tools@90c78712767e - novox/mesh-controller@175b28ee421f before novox/mesh-tools@90c78712767e: built by - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **Machines** - mesh-tools on every machine running it: sent - node-tools on ace: passed — healthy 3 times over 2m52s - node-tools on g14: failed — carried by release-1791457717307061152 - node-tools on novox: passed — carried by plan-1791457623441020580 - node-tools on the rest running it: sent **Transitions** - 2026-10-08 09:30 (new) → proposed (announced): novox/mesh-tools#22's head announced - 2026-10-08 09:33 proposed → checked (checked): the verdict names this commit - 2026-10-08 09:33 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 11:07 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:07 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path - 2026-10-08 11:22 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Author
Contributor

Merge check at 90c78712

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)
  • mesh/repo-check: PASS — its merge-check.sh passed

Delivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-tools, node-tools
  • ace: receives node-tools
  • g14: receives node-tools
  • novox: receives node-tools
  • shanks: receives node-tools
  • node-tools provides mcp-endpoint: its consumers are sent again after it

Run by the build seat on novox as build-1791451816448986017 (builds --log build-1791451816448986017).

--- the gate: mesh-tools, node-tools
mesh-tools: ok
node-tools: ok, invokes every tool
long-running resources without health: 0
2 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T09:29:30Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-08T09:29:30Z

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 2 module(s) in 1 tier(s): mesh-tools, node-tools
--- its merge-check.sh (go toolchain)
NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk
?   	github.com/novox/mesh-tools/node-tools/cmd/node-tools	[no test files]
ok  	github.com/novox/mesh-tools/node-tools/internal/alive	1.191s
ok  	github.com/novox/mesh-tools/node-tools/internal/announce	4.373s
ok  	github.com/novox/mesh-tools/node-tools/internal/bus	1.948s
ok  	github.com/novox/mesh-tools/node-tools/internal/launch	1.050s
ok  	github.com/novox/mesh-tools/node-tools/internal/meshtest	1.133s
?   	github.com/novox/mesh-tools/node-tools/internal/wire	[no test files]
ok  	github.com/novox/mesh-tools/node-tools/internal/console	0.005s
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry
**Merge check** at `90c78712` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step - tier 0: mesh-tools, node-tools - ace: receives node-tools - g14: receives node-tools - novox: receives node-tools - shanks: receives node-tools - node-tools provides mcp-endpoint: its consumers are sent again after it Run by the build seat on novox as `build-1791451816448986017` (`builds --log build-1791451816448986017`). ``` --- the gate: mesh-tools, node-tools mesh-tools: ok node-tools: ok, invokes every tool long-running resources without health: 0 2 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-08T09:29:30Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-08T09:29:30Z machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 2 module(s) in 1 tier(s): mesh-tools, node-tools --- its merge-check.sh (go toolchain) NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk ? github.com/novox/mesh-tools/node-tools/cmd/node-tools [no test files] ok github.com/novox/mesh-tools/node-tools/internal/alive 1.191s ok github.com/novox/mesh-tools/node-tools/internal/announce 4.373s ok github.com/novox/mesh-tools/node-tools/internal/bus 1.948s ok github.com/novox/mesh-tools/node-tools/internal/launch 1.050s ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.133s ? github.com/novox/mesh-tools/node-tools/internal/wire [no test files] ok github.com/novox/mesh-tools/node-tools/internal/console 0.005s NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry ```
mesh-admin merged commit d4845f7c8d into main 2026-10-08 11:06:23 +00:00
mesh-admin deleted branch fix/314-a-large-answer-is-paged-not-lost 2026-10-08 11:06:23 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-tools#22