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

remove what no longer has a reader: build-log store, dashboard sent/delivered events, graph resource dep

Browse source
This commit is contained in:
atlas 2026-11-13 10:08:19 +01:00 • committed by mara
commit 49266e4410
1 changed files with 204 additions and 1054 deletions
Download patch file Download diff file Expand all files Collapse all files

45
docs/4-implementation/agent-state/persistence.md
View file

@ -142,45 +142,20 @@ hive-c0re reads this file on each `build_all` sweep (~10s) via
sentinel files (`hyperhive-rate-limited`, `hyperhive-needs-login`) when the
JSON is absent.
### `/var/lib/hyperhive/db/build_logs.sqlite` (host)
### Container-operation logs (host)
Full stdout + stderr capture for every `nixos-container` / `nix
build` invocation the lifecycle layer fires. One row per invocation;
the row accumulates lines as the child runs.
Capturing the full stream (rather than a short tail buffer) matters
because real eval errors routinely run long — "tried alternatives"
blocks alone are often 30+ lines — so a truncated tail would cut off
the actual failure and leave only the host journal holding the
complete output. This table holds the entire log; no HTTP route serves
it.
Three indices:
- `(agent, started_at)` — per-agent lookup by recency.
- `(status, finished_at)` — backs the retention sweep that runs
as part of the existing hourly vacuum.
- `(node_id)` — added by a later migration so a build log row can be
looked up by the job-queue node it belongs to (a `hive_jobq` node is
immutable after insert, so hive-c0re records the link on the log row
instead); `node_id` is nullable.
Writes are best-effort: `append_stdout` / `append_stderr` / `finish`
log a warning on sqlite error and let the build continue. A failed
log row never blocks a rebuild.
Each operation also logs to the host journal, target `nixos-container`, and the
swarm log store collects those lines. Every line carries `build_id` (this
table's row id; empty without the store), `agent`, `kind` and `cmdline`. A
hive-c0re keeps no database of `nixos-container` / `nix build` output. Each
operation logs to the host journal, target `nixos-container`, and the swarm log
store collects those lines. Every line carries `agent`, `kind` and `cmdline`. A
`start` line (`event=start`) opens the build, one line follows per line of
output, and a `finish` line (`event=finish`) closes it with `status` (`ok` or
`fail`) and `runtime_secs`. hive-c0re logs a nix warning or error at warn, and a failed
finish too.
`fail`) and `runtime_secs`. hive-c0re logs a nix warning or error at warn, and a
failed finish too. A failed `start` also logs its error and the container
unit's journal tail.
A row is open (`finished_at IS NULL`) only while its child runs. At startup
`Coordinator::open` closes every row still open as `fail` and appends a
line saying hive-c0re stopped: the previous process died mid-build, and
the retention sweep never deletes open rows.
An earlier hive-c0re stored the same output in
`/var/lib/hyperhive/db/build_logs.sqlite`. Nothing reads or writes that file now, and
hive-c0re leaves it on disk untouched.
### `/harness/hyperhive-model` (per agent)