Register R327: a verb that only reads opens no bus connection of its own (hq issue 327)
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-group group fix/327-a-verb-reads-on-the-serving-connection checking: 3 of 4 member(s) ready
mesh/delivery superseded: a newer head of the same pull request

This commit is contained in:
jochen
2026-10-08 17:55:52 +02:00
parent 96b05fbd85
commit c54400cc69
+10
View File
@@ -231,6 +231,16 @@ var Register = []Replay{
Asserts: "a tool check on the NATS link the node-engine attaches reaches that link, and is not refused as no link",
Package: "./internal/link", Test: "TestReplay331", Files: []string{"internal/link/replay331_test.go"},
Home: "mesh-host", HomeRef: "5684a4579d92"},
// Every verb opened a bus connection of its own (2026-10-08): the server's connection total rose by 5.2 a
// minute while the same 16 stayed open, and three conditions calls in one second added three, each a
// process of the controller's binary that dialled, logged in and left. A test in the controller, written
// with only what it had before the fix, laid over the commit before. The fix is still on its branch: Fix
// is its pull request's head, proved against the main it is cut from.
{ID: "R327", Issue: 327, Kind: InRepository, Repository: "mesh-controller", Fix: "63e5e3b", Before: "0cf5a3a",
What: "three calls of conditions in one second added three connections to the bus: each verb ran as a " +
"process that dialled it, and hundreds of such connections an hour hid any client reconnecting",
Asserts: "a verb that only reads, served by the serving controller, opens no connection of its own",
Package: "./cmd/mesh-controller", Test: "TestReplay327", Files: []string{"cmd/mesh-controller/replay327_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.