Issue 331: resolve it, now the sensors condition is seen to clear on the laptop

2026-10-08 17:12:50 +02:00
parent a97efa99f8
commit 7d60650ae7
2 changed files with 13 additions and 1 deletions
@@ -1,5 +1,5 @@
 ---
-status: located
+status: resolved
 opened: 2026-10-08
 located-in: [mesh-host internal/link (hearing_nats.go, the NATS link; queue.go, AskTool)]
 fixed-by: novox/mesh-host PR #57, novox/mesh-host PR #58, novox/mesh-lab PR #69
@@ -42,3 +42,15 @@ the NATS link's interfaces; and distinct words for a link that cannot ask. The s
 check's error once (the evidence read "asking it: asking …"), says a deadline as "no answer within" the
 time the check gave it, and names a refusal only when the bus refused this question: the client keeps its
 last error for the life of the connection, so a refusal under a grant since widened was said again.
+
+## 2026-10-08, resolved
+
+**Seen live.** The node-engine with the fix (pull request 57, merged as `824911d`) passed its gate on
+the first machine after 2 minutes 18 seconds, healthy three times. It was sent to the laptop at
+15:10:11 UTC, and the laptop reported it applied at 15:10:33 UTC. The sensors condition on the laptop,
+raised at 13:26 UTC after 449 failed looks, cleared at 15:10:33 UTC. `mesh-controller.conditions`
+gave the reason as "no resource of sensors is unhealthy". Afterwards the laptop said its process
+`sensors.watch` was healthy, and no machine is behind on the node-engine.
+
+**The replay.** R331 in mesh-lab's replays register, `TestReplay331` in the node-engine, fails on the
+commit before the fix with "no link to the bus is open" and passes on it.