From 216af3826e6dce1516d36b6f99a9335f276dee35 Mon Sep 17 00:00:00 2001 From: Joshua Garnett Date: Sun, 9 Aug 2026 14:16:59 -0400 Subject: [PATCH] fix(responses): log the bridge check failure lazily The debug call built its message with an f-string, which test_logging_calls_do_not_build_their_message_eagerly rejects. Pass the exception as a %-style argument so the message is only built when the log is emitted. --- .../litellm_completion_transformation/transformation.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/litellm/responses/litellm_completion_transformation/transformation.py b/litellm/responses/litellm_completion_transformation/transformation.py index 8d790024cfe..c7f8ab24de4 100644 --- a/litellm/responses/litellm_completion_transformation/transformation.py +++ b/litellm/responses/litellm_completion_transformation/transformation.py @@ -337,7 +337,7 @@ class LiteLLMCompletionResponsesConfig: api_base=api_base, ) except Exception as e: # noqa: BLE001 # a capability probe must never fail the request it probes for - verbose_logger.debug(f"responses bridge: reasoning effort mode check failed: {e}") + verbose_logger.debug("responses bridge: reasoning effort mode check failed: %s", e) return False return model_info.get("mode") == "responses"