Registers issue 306, located, with the fix in novox/mesh-controller PR #133.
The packages that never touch a store run equally fast on every holder. The store-bound packages run five to seven times slower on the control node. Every controller check that landed there ran past the suite's 30-minute timeout.
Cause: the throwaway store runs with full durability, and its flushes go to a disk the mesh's own store, bus and forge keep busy. It wrote 16-20 GB per check.
Also: a holder recreated mid-check left its store and bus running, and the redelivery went to another machine. Eleven pairs were left across the four machines.
The 19-21 minutes "in flight" were several deliveries of the same check, each ended by a plan recreating the build agent.
Registers issue 306, located, with the fix in novox/mesh-controller PR #133.
- The packages that never touch a store run equally fast on every holder. The store-bound packages run five to seven times slower on the control node. Every controller check that landed there ran past the suite's 30-minute timeout.
- Cause: the throwaway store runs with full durability, and its flushes go to a disk the mesh's own store, bus and forge keep busy. It wrote 16-20 GB per check.
- Also: a holder recreated mid-check left its store and bus running, and the redelivery went to another machine. Eleven pairs were left across the four machines.
The 19-21 minutes "in flight" were several deliveries of the same check, each ended by a plan recreating the build agent.
Store-bound packages ran five to seven times slower there while the rest
ran alike: the throwaway store flushes to a disk the mesh's own data keeps
busy. And a holder recreated mid-check left its store and bus running.
Deliverynovox/hq@db0fea6067ba — delivered since 2026-10-08T08:35:43Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-08 08:22 (new) → proposed (announced): novox/hq#191's head announced
2026-10-08 08:23 proposed → checked (checked): the verdict names this commit
2026-10-08 08:23 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 08:35 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 08:35 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-delivery:view -->
**Delivery** `novox/hq@db0fea6067ba` — **delivered** since 2026-10-08T08:35:43Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-08 08:22 (new) → proposed (announced): novox/hq#191's head announced
- 2026-10-08 08:23 proposed → checked (checked): the verdict names this commit
- 2026-10-08 08:23 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-08 08:35 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 08:35 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`.
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.
Registers issue 306, located, with the fix in novox/mesh-controller PR #133.
The 19-21 minutes "in flight" were several deliveries of the same check, each ended by a plan recreating the build agent.
Delivery
novox/hq@db0fea6067ba— delivered since 2026-10-08T08:35:43ZDelivery 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.