jschoubben
2bee70a478
mesh/delivery-group group fix/529-a-waiting-walk-is-answered-or-named checking: 0 of 2 member(s) ready
mesh/merge-gate pass: builds mesh-delivery → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery superseded: a newer head of the same pull request
A merge whose plan sends nothing is delivered at once, yet the controller can still open a walk for it; no live delivery then held the walk and it waited for a person (the nzbgeek case). Give such a walk its word. Name each held delivery in the status, and let stalled say, for every waiting walk, what holds it, so the controller's plans line points at the person's decision instead of a hand start.