Watch
0
0
Fork
You've already forked hyperhive
0

hive-matrix-mcp: demote backup-key WARN where it actually runs, not just the fallback

This commit is contained in:
damocles 2026-10-07 23:48:16 +02:00 • committed by mara
commit a28163a008
2 changed files with 12 additions and 4 deletions

View file

@ -88,9 +88,11 @@ async fn main() -> Result<ExitCode> {
tracing_subscriber::EnvFilter::try_from_default_env().unwrap_or_else(|_| {
// matrix-sdk-crypto's own WARN fires every sync tick on any
// account with no key-backup set up (the common case here) —
// ~1/2s/host swarm-wide, the single largest log message by
// count. Demoted only in the no-RUST_LOG default, so an
// operator's explicit override still sees it if they ask.
// measured at ~76k lines/day swarm-wide, the single largest
// log message by count. The unit normally sets RUST_LOG
// explicitly (see matrix.nix), so this fallback mainly
// covers a bare `cargo run`; an operator's explicit
// override still sees it if they ask.
tracing_subscriber::EnvFilter::new("info,matrix_sdk_crypto::backups=error")
}),
)

View file

@ -315,7 +315,13 @@ in
# matrix sweep pushes unread-room + pending-invite todos here
# instead of firing wakes at hive-c0re's mcp.sock.
HIVE_AGENT_SOCKET = "/run/hive-agent/${userName}/agent.sock";
RUST_LOG = "info";
# matrix-sdk-crypto's own backup-key WARN fires every sync tick on
# any account with no key-backup set up (all of ours) — demoted
# here, not just in the binary's own no-RUST_LOG fallback, because
# this unit always sets RUST_LOG and the fallback never runs
# otherwise. An operator overriding RUST_LOG for debugging can
# still add `matrix_sdk_crypto::backups=warn` back explicitly.
RUST_LOG = "info,matrix_sdk_crypto::backups=error";
}
# The store's coordinates and which agent this is, so the daemon reads
# `swarm/agents/<agent>/matrix/<account>` as itself. The NAME and not a