version mismatch catch

This commit is contained in:
ari committed 2026-11-01 14:34:23 -05:00
1 parent 3ba96528bb
commit a90653260a
11 files changed
+181 -34

No files matched your search

+1
View File
@@ -46,6 +46,7 @@ flowchart LR
- The slave connects to `wss://master/cluster` with `X-Cluster-Secret` and `X-Node-Name`, and pins the master's self-signed certificate by fingerprint, either from the config or trusted on first use.
- Frames are JSON: `call`/`reply` for node operations, `report` for node info every 5s, and `data`/`close` for byte streams. Agent connections are tunnelled as streams.
- Each `report` carries the slave's build version. The bot compares it with the master's and flags any difference at the top of `help`, `nodes` and `status`. A slave that reports no version (an older build) counts as a mismatch.
- A slave that hasn't reported for 20s, or whose link has dropped, counts as offline. The master doesn't trust reports for a short while after it asks a slave to start or stop something, so stale reports don't undo the change.
## Migration