Prove R330 against the merge of its fix
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

This commit is contained in:
jochen
2026-10-08 21:15:36 +02:00
parent 54db7c3458
commit f91164863b
+3 -3
View File
@@ -234,9 +234,9 @@ var Register = []Replay{
// 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. The
// fix is still on its branch: Fix is its pull request's head, proved against the main it is cut from.
{ID: "R330", Issue: 330, Kind: InRepository, Repository: "mesh-controller", Fix: "909062e", Before: "e3ec15f",
// 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 " +