Register R233: a declaration that restores the package manager applies while it does not answer (hq issue 233) #84

Merged
mesh-admin merged 1 commits from fix/233-replay-2 into main 2026-10-12 14:53:25 +00:00
+15
View File
@@ -342,6 +342,21 @@ var Register = []Replay{
Asserts: "every line of assign's answer is derived from one resolution of the node taken after the " +
"write committed, and agrees with plan for the node run right after the act",
Package: "./cmd/mesh-controller", Test: "TestReplay237", Files: []string{"cmd/mesh-controller/replay237_test.go"}},
// A host without its package manager's configuration refused the declaration that would restore it
// (2026-10-04): a declaration that left the package manager's module out removed pacman's configuration
// file; from then on pacman did not answer, and the node-engine refused every declaration whole, the
// one that named the module again and would have written the file back included. A person restored the
// file by hand an hour and a half later. A test in the node-engine, written only with what it had before
// its fix, laid over the commit before (mesh-host #90). Fix is the merge of its pull request. The
// controller's half of the fix (mesh-controller #263, db7e4869: a machine refused or applied only partly
// past one apply interval raises a condition) is held by its own tests there, not by this replay.
{ID: "R233", Issue: 233, Kind: InRepository, Repository: "mesh-host", Fix: "a1f9856b3957fa0b11c04294f6367bc6febf5eb0",
What: "the package manager's configuration file was removed, pacman stopped answering, and the node-engine " +
"refused every declaration whole, the one that would have written the file back included",
Asserts: "a declaration that restores the package manager's configuration is applied while pacman does not " +
"answer: only what needs pacman fails, with the probe's words, and the file is written and recorded",
Package: "./cmd/mesh-host", Test: "TestReplay233",
Files: []string{"cmd/mesh-host/replay233_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.