Register R336: a send held for the bus's planned step is told to the operator
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript), replays/merge-check.sh (go)
mesh/delivery delivered

hq issue 336 is a core issue and resolves with its replay. TestReplay336 in the controller, merged with
#173 (b13a0f7), fails on its first parent and passes on it: prove R336 says PROVED.
This commit is contained in:
jochen
2026-10-09 09:25:29 +02:00
parent aaca73afb2
commit fb5bb1e3de
+12
View File
@@ -263,6 +263,18 @@ var Register = []Replay{
Asserts: "once a build passed its gate, the first machine's later reports neither fail it nor hold the rest, " +
"and a walk stopped after the pass keeps it",
Package: "./cmd/mesh-controller", Test: "TestReplay335", Files: []string{"cmd/mesh-controller/replay335_test.go"}},
// A send held for the bus's planned step said nothing (2026-10-08): a catalogue merge built a new bus for the
// control-node, every send to that machine was refused for 28 minutes for a step only a person starts, and
// nothing but the walks' notes said so. A test in the controller, written with only what it had before the
// fix, laid over the commit before. Fix is the merge of its pull request (mesh-controller #173), proved
// against its first parent.
{ID: "R336", Issue: 336, Kind: InRepository, Repository: "mesh-controller", Fix: "b13a0f7",
What: "for 28 minutes every send to the control-node was refused for a new bus build waiting for a " +
"person's bus upgrade, and no condition said so",
Asserts: "the first watchdog tick after a send is refused for the bus's planned step opens a condition for " +
"the operator naming what waits and the call that ends it, and it clears once the machine is sent the " +
"new bus",
Package: "./cmd/mesh-controller", Test: "TestReplay336", Files: []string{"cmd/mesh-controller/replay336_test.go"}},
// Not a core incident, and the first of its kind: a module's. The crash loop was found by a person
// reading the agent server's log for another reason (issue 268); research 032 measured it, and ADR
// 0240 makes the node-engine judge it and the gate fail it.