The hub keeps every machine's sampling rate and history window in step

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-21 10:14:23 -07:00
parent 668e716601
commit be0f2a5aaf
2 changed files with 59 additions and 5 deletions
@@ -478,6 +478,14 @@ is 11px wide" at 1392); run after, nothing, in both browsers.
 9. ✅ **Idle curves vanished**: a core at 10 % rounded to no dots at all in its mini graph.
   Anything above zero lights the bottom row, which is also btop's rule.

+10. ✅ **Found by the deploy of fix 2 itself: telling the machines once is not enough.** The hub
+    restarted first and told three nodes that did not yet have the endpoint (404); they then
+    updated and carried on at 1 s. The same would happen to any node that is off or
+    restarting when a setting changes. The hub now *keeps* the fleet in step: fifteen seconds
+    after it starts and every two minutes after, it asks each machine for its sampling rate
+    and history window and corrects only what differs (logged as `fleet: grid had ms=1000,
+    now 250`).
+
 ## Skins

 ✅ Top now wears the skin. The ground is the skin's terminal background and every curve and