| Filename | Latest commit message | Latest commit date |
|---|---|---|
36918e0432
Review catch from argus on #2770: with the terminal hook gone, cancel spares the DAG's tail node so it can report the cancellation — which leaves that node `Pending` until the scheduler's next pass. `post_rebuild_queue_cancel` emits its snapshot synchronously, and `rollup_state` ranked `Queued` above `Cancelled`, so the operator who just cancelled a DAG saw it go back to **Queued**: "the cancel didn't take". Asserted in `cancel_clears_queued_dag`, which failed before this. Fixing it surfaced an older disagreement. `builds.js::rollupState` has always been `failed > cancelled > running > queued`; the Rust was `failed > running > queued > cancelled`. The two had silently diverged under a doc-comment claiming they agree. Harmless until now only because cancelled nodes never coexisted with live ones — a spared tail running over cancelled work would have rendered `Running` host-side and `Cancelled` in the dashboard. The JS was the correct side, so the Rust moves to match it exactly: `Failed > Cancelled > Running > Queued > Done`. No frontend change. |
||
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
hive-host-sock
Wire types for the host admin socket (/run/hyperhive/host.sock) — the
host-control protocol spoken between the hivectl operator CLI and the
hive-c0re daemon.
Why it's its own crate
Re-homed out of hive-sh4re so a standalone hivectl depends on just this
protocol crate instead of the whole daemon-shared crate. hivectl drives the
full hive (spawn / kill / destroy / rebuild / deploy) over this socket without
linking hive-c0re; keeping the request/response shapes here is what makes that
thin dependency possible.
Shape
Serde-derived request/response enums for the host admin protocol. The larger
shared payload types some variants reference (Approval, AgentStatusRow,
jobs::DagView) stay in hive-sh4re — this crate is only the protocol
envelope, no server or client implementation.
See docs/boundary.md (host admin socket access) for the trust model around who
may connect to the socket, and hive-priv-sock for the sibling split on the
privileged-helper socket.