synology_apm_repo.sdk.presentation.logging_setup module¶
Silencing dependency logging before it reaches the CLI/TUI’s own output — shared by both surfaces since they must behave identically here: a per-surface copy would let a future fix (encoding, handler behavior, …) land in only one of them.
With no handler configured anywhere, logging falls back to its
last-resort handler, which writes every WARNING and above straight to
stderr — smbprotocol alone emits one per pooled connection each time a
session is torn down. A NullHandler on the root logger is what stops
that: Logger.callHandlers only reaches the last-resort path when it
finds no handler at all.
- synology_apm_repo.sdk.presentation.logging_setup.configure_logging()¶
Adds a
NullHandlerto the root logger, or redirects everything to a file named byLOG_FILE_ENVinstead, for when a backend actually needs debugging.