hq issue 335: dunst's build passed its gate on the laptop and was marked failed at its gate, and put back, 28 minutes later, because the plan read the laptop's silence about another walk's send as the passed build never applied.
R335 is TestReplay335 in mesh-controller (#165), written with only what the controller had before the fix.
Proved with go run ./replays/cmd/prove R335: fails on 7f65e62 (main), passes on becd40b (the fix's head):
R335 (issue 335): PROVED — before its fix fails, on its fix passes
replays/merge-check.sh passes locally. Once mesh-controller#165 merges, Before is cleared and Fix points at the merged commit.
hq issue 335: dunst's build passed its gate on the laptop and was marked failed at its gate, and put back, 28 minutes later, because the plan read the laptop's silence about another walk's send as the passed build never applied.
R335 is `TestReplay335` in mesh-controller (#165), written with only what the controller had before the fix.
Proved with `go run ./replays/cmd/prove R335`: fails on 7f65e62 (main), passes on becd40b (the fix's head):
R335 (issue 335): PROVED — before its fix fails, on its fix passes
`replays/merge-check.sh` passes locally. Once mesh-controller#165 merges, `Before` is cleared and `Fix` points at the merged commit.
Deliverynovox/mesh-lab@06fa70d081fc — delivered since 2026-10-08T19:54:56Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-08 19:52 (new) → proposed (announced): novox/mesh-lab#72's head announced
2026-10-08 19:52 proposed → checked (checked): the verdict names this commit
2026-10-08 19:52 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 19:54 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 19:54 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/mesh-lab@06fa70d081fc` — **delivered** since 2026-10-08T19:54:56Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-08 19:52 (new) → proposed (announced): novox/mesh-lab#72's head announced
- 2026-10-08 19:52 proposed → checked (checked): the verdict names this commit
- 2026-10-08 19:52 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-08 19:54 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 19:54 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`.
hq issue 335: a build that passed its gate was failed and put back when the
first machine's later reports went quiet. Proved: fails on 8170fc5^1,
passes on 8170fc5.
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.
hq issue 335: dunst's build passed its gate on the laptop and was marked failed at its gate, and put back, 28 minutes later, because the plan read the laptop's silence about another walk's send as the passed build never applied.
R335 is
TestReplay335in mesh-controller (#165), written with only what the controller had before the fix.Proved with
go run ./replays/cmd/prove R335: fails on 7f65e62 (main), passes on becd40b (the fix's head):replays/merge-check.shpasses locally. Once mesh-controller#165 merges,Beforeis cleared andFixpoints at the merged commit.Delivery
novox/mesh-lab@06fa70d081fc— delivered since 2026-10-08T19:54:56ZDelivery 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.4928774650to06fa70d081