New issue record, status located. Console calls to mesh-controller.push timed out (54 of 103 pushes over two days) while the push happened. When a push sent the bus a changed user list, the broker reload forgot the controller's permission to reply, and the answer was refused. The only trace was the client library's journal line.
The fix is in mesh-controller (answer within 10 s or as running with a call id, a push answers before it sends, refused answers are recorded, new calls verb) and mesh-tools (a timeout says it is not a failure). fixed-by gets filled once those merge.
Checks: records.py, index.py, cycle.py pass.
New issue record, status located. Console calls to `mesh-controller.push` timed out (54 of 103 pushes over two days) while the push happened. When a push sent the bus a changed user list, the broker reload forgot the controller's permission to reply, and the answer was refused. The only trace was the client library's journal line.
The fix is in mesh-controller (answer within 10 s or as running with a call id, a push answers before it sends, refused answers are recorded, new `calls` verb) and mesh-tools (a timeout says it is not a failure). `fixed-by` gets filled once those merge.
Checks: records.py, index.py, cycle.py pass.
Deliverynovox/hq@64c2d3a0a11c — 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#122 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/hq@64c2d3a0a11c` — **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#122 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.
New issue record, status located. Console calls to
mesh-controller.pushtimed out (54 of 103 pushes over two days) while the push happened. When a push sent the bus a changed user list, the broker reload forgot the controller's permission to reply, and the answer was refused. The only trace was the client library's journal line.The fix is in mesh-controller (answer within 10 s or as running with a call id, a push answers before it sends, refused answers are recorded, new
callsverb) and mesh-tools (a timeout says it is not a failure).fixed-bygets filled once those merge.Checks: records.py, index.py, cycle.py pass.
Delivery
novox/hq@64c2d3a0a11c— 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 nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.