Prove R318 on the fix's head, which gives the new condition its plain words (hq issue 318)
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
mesh/delivery-group group fix/318-a-wait-for-a-person-is-not-a-failure delivered: every member is delivered

This commit is contained in:
jochen
2026-10-08 14:37:35 +02:00
parent 65ae6a9f89
commit 1455d9560e
+3 -1
View File
@@ -202,7 +202,9 @@ var Register = []Replay{
// needed and its daemon's unit failed in that account's manager, and the gate failed the send at its bound,
// put the module back (taking its account group back) and stopped every walk behind it. A test in the
// controller, reading the statements as the node-engine's JSON, so it is laid over the commit before.
{ID: "R318", Issue: 318, Kind: InRepository, Repository: "mesh-controller", Fix: "9b86fa9",
// Fix is the head of the fix: e3b5c22 alone raises the new condition kind without the plain words the
// controller's suite requires since hq ADR 0253, which 51d7bbf gives it. Before is the main both stood on.
{ID: "R318", Issue: 318, Kind: InRepository, Repository: "mesh-controller", Fix: "51d7bbf", Before: "6df30b6",
What: "a send of three modules to the laptop failed its gate after ten minutes because one module's account " +
"needed a new login; the module was put back and the walks of the other modules stopped behind it",
Asserts: "a wait for a person's new login passes the gate with the wait carried and said as the module's " +