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

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

Browse source
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
Download patch file Download diff file Expand all files Collapse all files

8
hive-matrix-mcp/src/main.rs
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")
}),
)