hive-matrix-mcp: demote backup-key WARN where it actually runs, not just the fallback
This commit is contained in:
parent
2835c08cb0
commit
a28163a008
2 changed files with 12 additions and 4 deletions
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Reference in a new issue