Quentin Gliech 0de7aa9953 Enable flake8-logging and flake8-logging-format rules in Ruff and fix related issues throughout the codebase (#18542) ... This can be reviewed commit by commit. This enables the `flake8-logging` and `flake8-logging-format` rules in Ruff, as well as logging exception stack traces in a few places where it makes sense - https://docs.astral.sh/ruff/rules/#flake8-logging-log - https://docs.astral.sh/ruff/rules/#flake8-logging-format-g ### Linting to avoid pre-formatting log messages See [`adamchainz/flake8-logging` -> *LOG011 avoid pre-formatting log messages*](152db2f167/README.rst (log011-avoid-pre-formatting-log-messages)) Practically, this means prefer placeholders (`%s`) over f-strings for logging. This is because placeholders are passed as args to loggers, so they can do special handling of them. For example, Sentry will record the args separately in their logging integration: c15b390dfe/sentry_sdk/integrations/logging.py (L280-L284) One theoretical small perf benefit is that log levels that aren't enabled won't get formatted, so it doesn't unnecessarily create formatted strings		2025-06-13 09:44:18 +02:00
..
__init__.py	Update license headers	2023-11-21 15:29:58 -05:00
test_matrix_federation_agent.py	Enable flake8-logging and flake8-logging-format rules in Ruff and fix related issues throughout the codebase (#18542)	2025-06-13 09:44:18 +02:00
test_srv_resolver.py	Format files with Ruff (#17643)	2024-09-02 12:39:04 +01:00