| Filename | Latest commit message | Latest commit date |
|---|---|---|
662e303e72
Fixes hyperhive#2895. The rebuild-queue tree's per-node log icon (the printer-glyph "open" affordance next to each node in the R3BU1LD QU3U3 tab) linked directly to the raw-text download endpoint (/api/build-log/<node_id>/raw, which sets Content-Disposition: attachment server-side) -- surprising, since nothing about that icon signals "this leaves the app", unlike the other two explicit "download raw"/"raw" links elsewhere on the page. Point it at the existing ?id=N#buildlogs deep-link into the BUILD L0GS tab instead (builds.js's fetchBuild already auto-expands + scrolls to the matching row there). That deep-link's id is the build-log history row id -- a different id space than the queue tree's NodeId, and wasn't exposed to the frontend before (only a derived has_log bool was). Added NodeView.build_log_id: Option<i64> to the wire type alongside the existing has_log (kept, since findLiveBuild's separate live-log-panel gate still needs a plain bool), threaded through job_queue::mod.rs, updated hivectl's NodeView test-helper literal. The raw download is still one click away once on that row's BUILD L0GS detail (the two already-explicit raw-download links are untouched). cargo build/clippy/test clean across the three touched crates (hive-c0re, hive-host-sock, hivectl); nix fmt clean; frontend build verified (grep for build_log_id in the built builds.js bundle). |
||
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
hive-c0re
The unprivileged host daemon (runs as hive-core). Owns the sqlite
broker, the approval/question/schedule queues, the generic job-DAG
queue, container lifecycle, gateway/forge/matrix provisioning,
per-container stats, and the axum operator dashboard. Largest crate in
the workspace — bin-only, no separate lib.
When to use it
Host-level, cross-container orchestration: spawning/rebuilding/
destroying agent containers, the approval flow, dashboard-visible
state, provisioning per-agent forge/matrix/gateway accounts. Agent-side
behavior (turn loop, MCP tools) lives in hive-agent/hive-agent-mcp
instead — this daemon only talks to agents over the socket wire types
in hive-sh4re.
Shape
Cohesive clusters live in directory submodules, each re-exported at
the crate root (crate::broker::… keeps resolving regardless of which
subdirectory a module actually lives in). One line each — read the
module's own //! doc-comment for real detail, don't expect this file
to track it:
dashboard/— the operator dashboard (containers, approvals, schedules, questions, logs, topology).job_queue/— the job-DAG queue + desired-state reconciliation (docs/coordinator.md).lifecycle/—nixos-containerlifecycle + per-agent config flake generation.stores/— sqlite-backed stores (broker, queues, audit, power).workers/— background sweeps (crash watch, scheduled prompts, auto-update, knowledge sync).agent_config/— per-agent registries (tool groups, capabilities, resource limits, topology).stats/— dashboard metrics aggregation + OTEL export.socket_server/— the unix-socket request server shared by per-agent + manager sockets.forge/— optional Forgejo wiring (docs/forge.md).coordinator.rs— top-level wiring forserve.meta.rs,migrate.rs— the meta flake + schema/state migrations.matrix.rs,gateway_nginx.rs,webhook_secret.rs,priv_client.rs— matrix provisioning, gateway vhosts, webhook secrets, and thehive-privclient respectively.
See the top-level CLAUDE.md/docs/ index for the full reading-path
map.