| Filename | Latest commit message | Latest commit date |
|---|---|---|
4c37ce9150
Per mara's review on #2896: has_log: bool was fully redundant once build_log_id: Option<i64> existed alongside it (has_log was always just build_log_id.is_some()). Dropped has_log, threading the single Option<i64> field through job_queue::mod.rs, the hivectl NodeView test-helper literal, and the one remaining frontend consumer (findLiveBuild's live-log-panel gate, which now checks build_log_id != null instead of the separate bool). Also fixed a now-stale doc comment on GET /api/build-log/{node_id} that claimed the dashboard used on-demand node-id fetches "instead of an inline build_log_id on the wire" -- no longer true after this PR put one there for the BUILD L0GS deep-link. cargo build/clippy/test clean across the three touched crates; nix fmt clean; frontend build verified (0 has_log references, 3 build_log_id references in the built builds.js bundle). |
||
| .. | ||
| 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.