novox/mesh-lab
6
0
Fork 0
Code Issues Pull Requests 2 Releases Wiki Activity

Merge pull request 'Register R331: a tool check is asked on the link the node-engine holds (hq issue 331)' (#69) from replays/331-a-tool-check-on-the-live-link into main

Browse Source
This commit was merged in pull request #69.
This commit is contained in:
mesh-admin
2026-10-08 15:17:24 +00:00
parent 24bc736393 3a3317b487
commit 96b05fbd85
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
replays/register.go
+10
View File
@@ -221,6 +221,16 @@ var Register = []Replay{
Asserts: "an assignment made while its module's build runs says the build, is kept, and is made when the " + Asserts: "an assignment made while its module's build runs says the build, is kept, and is made when the " +
"build registers the module", "build registers the module",
Package: "./cmd/mesh-controller", Test: "TestReplay325", Files: []string{"cmd/mesh-controller/replay325_test.go"}}, Package: "./cmd/mesh-controller", Test: "TestReplay325", Files: []string{"cmd/mesh-controller/replay325_test.go"}},
// A declared tool check never asked on a live machine (2026-10-08): the queue reached the bus through an
// assertion only OverNATS met, and the NATS link the node-engine attaches had no Ask, so every tool check
// read "no link to the bus is open" while the link was up. A test in the node-engine, written with only
// what it had before the fix; Home is its commit that added it.
{ID: "R331", Issue: 331, Kind: InRepository, Repository: "mesh-host", Fix: "824911d",
What: "the sensors module's tool check on the laptop read no link to the bus is open for hours while the " +
"node-engine's link was up and the same tool answered through the mesh MCP server",
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"},
// Not a core incident, and the first of its kind: a module's. The crash loop was found by a person // 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 // 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. // 0240 makes the node-engine judge it and the gate fail it.