The checker waits its compose answer bound, not the SDK's 30 s, for the machines' compositions #144

Merged
mesh-tools merged 2 commits from fix/1126-compose-answer-bound into main 2026-11-03 00:40:27 +00:00
Member

Under issue 1126 (note 140-141). The checker's composition ask went through mesh-sdk's process call, which gives up at CallTimeout = 30 s, so the compose-answer-bound of 60 s (ADR 0593 §7) never applied and every machine but the checker's own was named silent.

The checker raises process.CallTimeout to its answer bound at start (holdCallsFor), never lowering it; its other calls (forge reads) may now wait up to 60 s too. Quick fix: chosen. Thorough (a per-call deadline in mesh-sdk for every module): to be asked of the operator, as a mesh-sdk change. Test: rows in TestTheAnswerBoundIsTheCheckersSetting; fails without the fix.

Independent of mesh-host fix/1126-compose-wait (the node-engine answering in time); either may merge first.

Reviewed-by: review-1126-compose@shanks at bedda86a22

https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

Under issue 1126 (note 140-141). The checker's composition ask went through mesh-sdk's process call, which gives up at CallTimeout = 30 s, so the compose-answer-bound of 60 s (ADR 0593 §7) never applied and every machine but the checker's own was named silent. The checker raises process.CallTimeout to its answer bound at start (holdCallsFor), never lowering it; its other calls (forge reads) may now wait up to 60 s too. Quick fix: chosen. Thorough (a per-call deadline in mesh-sdk for every module): to be asked of the operator, as a mesh-sdk change. Test: rows in TestTheAnswerBoundIsTheCheckersSetting; fails without the fix. Independent of mesh-host fix/1126-compose-wait (the node-engine answering in time); either may merge first. Reviewed-by: review-1126-compose@shanks at bedda86a22c5f9e76172019a7da3213afe6d4e86 https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL
mesh-tools added 2 commits 2026-11-03 00:29:51 +00:00
Author
Member

Delivery novox/mesh-delivery@bedda86a22c5 — merged since 2026-11-03T00:40:28Z

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

Transitions

  • 2026-11-03 00:29 (new) → proposed (announced): novox/mesh-delivery#144's head announced
  • 2026-11-03 00:29 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-11-03 00:40 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-delivery:view --> **Delivery** `novox/mesh-delivery@bedda86a22c5` — **merged** since 2026-11-03T00:40:28Z **Source** — source.main moved to novox/mesh-delivery@8f83608503da. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-03 00:29 (new) → proposed (announced): novox/mesh-delivery#144's head announced - 2026-11-03 00:29 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-11-03 00:40 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 8f83608503 into main 2026-11-03 00:40:27 +00:00
mesh-tools deleted branch fix/1126-compose-answer-bound 2026-11-03 00:40:27 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-delivery#144