| Filename | Latest commit message | Latest commit date |
|---|---|---|
657d1b5061
A node ruled out by its own dependency edges settles `Skipped` host-side, but the wire folded it into `Cancelled` and `dag_view` filtered it out entirely, so a client never saw which branch a run didn't take. Post-#2785 that is not a rare shape: every approval DAG has two not-taken tails and every rebuild has one, on the happy path as much as on failure. `State` gains `Skipped`, and it counts as terminal — the wait loops in hivectl's progress display and the daemon's dag-settled check decide "finished" with `all(is_terminal)`, so omitting it would hang them on essentially every DAG. `dag_view` now emits skipped nodes but no longer lets them keep a DAG alive. Serialization and completion were the same expression: a DAG left the snapshot because its nodes had all been filtered away. Keeping skipped nodes on the wire under that rule would pin every finished deploy in the queue view forever, so the completion test is now its own flag. `rollupState` in the dashboard gains the matching arm. It has no `done` case — `done` is inferred by falling off the wire — so its trailing `return 'queued'` catches anything it doesn't recognise, and a green deploy would have read as permanently queued the moment the backend started emitting the new state. The Rust and JS roll-ups have silently disagreed before; they are edited together here and say so. |
||
| .. | ||
| 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.