vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

hive-c0re: replace the agents_crashing banner with a crash-watcher log line + grafana alert

Browse source
This commit is contained in:
damocles 2026-10-12 22:21:04 +02:00 • committed by mara
commit 02831fb5e9
13 changed files with 214 additions and 224 deletions
Download patch file Download diff file Expand all files Collapse all files

13
docs/turn-loop/mcp.md
View file

@ -62,12 +62,13 @@ is opt-in via the P3RM1SS10NS tab.
Transient pings (sentinel id 0) have nothing to ack and show no marker.
**System messages** (from sender `system`): the broker delivers
`hive_sh4re::manager::HelperEvent` (two variants: `ContainerCrash`,
`NeedsUpdate` — declared, but no call site constructs it) as regular
inbox messages (same `recv` path; body is a JSON object with an `event`
discriminant field).
`ContainerCrash` always goes to `ruth` (`Coordinator::notify_manager`,
hardcoded — `hive-c0re/src/workers/crash_watch.rs`). Lifecycle
`hive_sh4re::manager::HelperEvent` (one variant, `NeedsUpdate` —
declared, but no call site constructs it) as regular inbox messages
(same `recv` path; body is a JSON object with an `event` discriminant
field). A container crash used to be the other variant
(`ContainerCrash`, routed to `ruth`) but that path is gone — a crash
now only produces a log line + swarm-level grafana alert, no agent
turn at all (`docs/scheduler/observability.md`). Lifecycle
transitions the job-queue scheduler or crash watcher drive directly —
stop/kill, destroy, a flake-rev login or logout state change — reach
no individual agent: they publish onto a swarm-wide NATS