hyperhive/hive-c0re
Repository files (latest commit first)
Filename Latest commit message Latest commit date
iris b63738e8c2 fix(#2289): wire ci-runner registration failures to dashboard warning banner
Both warn!-and-forget sites in ensure_ci_runner_registered() now also
call set_boot_warning():

- fetch_registration_token failure → crit banner (forge unreachable or
  API error; runner stays with stale/absent creds)
- hive-priv register_ci_runner failure → crit banner (EROFS or priv
  socket error; runner token not written)

Both are only ever invoked from ensure_all() at hive-c0re startup (no
periodic retry), so set_boot_warning() is the right API: the banner
persists until the next c0re restart that re-runs the step, which is
exactly when a config/environment fix (e.g. the ReadWritePaths EROFS
fix from 64075107) would take effect.

Journal warn! lines are kept alongside the banner (belt-and-suspenders).

Remaining in scope for #2289: sync_agent() warn! sites (called from
both startup and rebuild paths — needs set_warning RAII or explicit
return value to enable later success to clear the banner; left for a
follow-up).
2026-07-19 14:17:53 +02:00
..
src fix(#2289): wire ci-runner registration failures to dashboard warning banner 2026-07-19 14:17:53 +02:00
Cargo.toml feat(#2007): export per-agent container cpu/mem/disk via otel 2026-07-15 22:51:31 +02:00