The console's timeout read "did not answer in time … the tool being slow", and operators took it as failed and pushed again. The push had happened. Now a timeout says it is not a failure: the call may still be running and may already have done what was asked, so check before repeating a call that changes the mesh. For mesh-controller.* it adds that the controller answers within seconds, so the answer was lost on the way, and mesh-controller.calls has it. That verb comes with the companion mesh-controller PR, which also makes the controller answer within 10 s, well inside the console's 30 s RequestTimeout. A comment on RequestTimeout records that relationship.
Test: TestATimeoutIsNotAFailure. gofmt, go vet ./..., go test ./... in node-tools are clean.
novox/hq issue 265.
The console's timeout read "did not answer in time … the tool being slow", and operators took it as failed and pushed again. The push had happened. Now a timeout says it is not a failure: the call may still be running and may already have done what was asked, so check before repeating a call that changes the mesh. For `mesh-controller.*` it adds that the controller answers within seconds, so the answer was lost on the way, and `mesh-controller.calls` has it. That verb comes with the companion mesh-controller PR, which also makes the controller answer within 10 s, well inside the console's 30 s `RequestTimeout`. A comment on `RequestTimeout` records that relationship.
Test: `TestATimeoutIsNotAFailure`. gofmt, go vet ./..., go test ./... in node-tools are clean.
Deliverynovox/mesh-tools@730b4047f0f2 — 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 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
Transitions
2026-10-06 23:05 (new) → proposed (announced): novox/mesh-tools#15 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.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-tools@730b4047f0f2` — **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 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
**Transitions**
- 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-tools#15 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`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
novox/hq issue 265.
The console's timeout read "did not answer in time … the tool being slow", and operators took it as failed and pushed again. The push had happened. Now a timeout says it is not a failure: the call may still be running and may already have done what was asked, so check before repeating a call that changes the mesh. For
mesh-controller.*it adds that the controller answers within seconds, so the answer was lost on the way, andmesh-controller.callshas it. That verb comes with the companion mesh-controller PR, which also makes the controller answer within 10 s, well inside the console's 30 sRequestTimeout. A comment onRequestTimeoutrecords that relationship.Test:
TestATimeoutIsNotAFailure. gofmt, go vet ./..., go test ./... in node-tools are clean.Delivery
novox/mesh-tools@730b4047f0f2— held since 2026-10-06T23:05:28ZHeld for a person: merged without a passing check: only a person decides that it goes on —
mesh-delivery.releasewith why lets it go on.Delivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.