Register R330: a message a consumer gave up on is kept (hq issue 330) #70

Merged
mesh-admin merged 2 commits from fix/330-a-message-given-up-on-is-kept into main 2026-10-08 19:27:04 +00:00
+11
View File
@@ -231,6 +231,17 @@ 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"},
// Messages a consumer gave up on were kept nowhere (2026-10-06): a media server's consumer gave up on
// several downloads after five deliveries each, the controller's condition cleared within minutes, and
// EVENTS dropped them a week later; the dead-letter stream design 25 promised did not exist. A test in
// the controller, written with only what the link had before the fix, laid over the commit before. Fix is
// the merge of its pull request, proved against its first parent.
{ID: "R330", Issue: 330, Kind: InRepository, Repository: "mesh-controller", Fix: "ca09a07",
What: "a media server's event consumer gave up on several messages after five deliveries each; the condition " +
"cleared within minutes and nothing kept which messages they were",
Asserts: "a consumer that never acknowledges an event gives it up, and the event is kept on the bus with " +
"its consumer, stream, subject, deliveries and when it was given up",
Package: "./internal/link", Test: "TestReplay330", Files: []string{"internal/link/replay330_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.