scriptoriumadmin/litellm
1
0
Fork 0
mirror of https://github.com/BerriAI/litellm.git synced 2026-10-29 06:33:28 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 267

trim excessive comments in tool_choice fix

Browse source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
TobiMayr 2026-07-14 17:55:34 +01:00
parent 996031b471
commit 84e1bf73c0
2 changed files with 7 additions and 35 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
litellm/responses/litellm_completion_transformation/streaming_iterator.py
View file

@ -336,12 +336,8 @@ class LiteLLMCompletionStreamingIterator(ResponsesAPIStreamingIterator):
if "text" in self.responses_api_request:
response_created_event_data["text"] = self.responses_api_request["text"]
if "tool_choice" in self.responses_api_request:
# Normalize tool_choice to the shape ResponsesAPIResponse.tool_choice
# accepts (flat {"type": "function", "name": "..."}), not the Chat
# Completion nested {"type": "function", "function": {"name": "..."}}
# shape that _transform_tool_choice produces for the outbound provider
# call. Reusing that Chat-Completion-shaped value here fails Pydantic
# validation for any forced named tool call.
# Use the Responses-API-shaped value here, not _transform_tool_choice's
# Chat Completion shape, or forced named tool calls fail Pydantic validation.
response_created_event_data["tool_choice"] = (
LiteLLMCompletionResponsesConfig._transform_tool_choice_for_responses_api_response(
self.responses_api_request["tool_choice"]

34
litellm/responses/litellm_completion_transformation/transformation.py
View file

@ -171,35 +171,11 @@ class LiteLLMCompletionResponsesConfig:
tool_choice: Any,
) -> str | dict[str, Any] | None:
"""
Transform tool_choice into the shape the Responses API's own
``ResponsesAPIResponse.tool_choice`` field accepts.
This is the inverse of ``_transform_tool_choice``: that function
converts an incoming Responses-API-shaped tool_choice into Chat
Completion format so it can be sent to the provider. But the
streaming iterator also needs a tool_choice value to echo back on
the synthetic ``response.created``/``response.in_progress`` events,
and those events are validated against the Responses API schema, not
the Chat Completion one. Reusing the Chat-Completion-shaped value
there fails validation for a forced named tool call, since OpenAI's
Responses API ``ToolChoiceFunctionParam`` is the flat
``{"type": "function", "name": "..."}``, not Chat Completion's
nested ``{"type": "function", "function": {"name": "..."}}``.
Delegates to ``_transform_tool_choice`` first to normalize any
Cursor-IDE-style dict input (e.g. {"type": "tool"}, {"type":
"function"} without a name) into a string or the Chat Completion
nested shape, then rewrites only the nested-function case into the
flat Responses API shape.
Handles:
- String values: "auto", "none", "required" -> pass through as-is
- Dict with type only (Cursor IDE format), normalized the same way
as _transform_tool_choice: {"type": "auto"/"none"/"required"/
"tool"/"any"} -> the corresponding string
- Chat Completion nested function format:
- {"type": "function", "function": {"name": "..."}} -> {"type": "function", "name": "..."}
- Already-flat Responses API format: pass through as-is
Inverse of ``_transform_tool_choice``: normalizes tool_choice into the
shape ``ResponsesAPIResponse.tool_choice`` accepts (flat
``{"type": "function", "name": "..."}``), not Chat Completion's nested
``{"type": "function", "function": {"name": "..."}}``, which fails
Pydantic validation on this field.
"""
normalized = LiteLLMCompletionResponsesConfig._transform_tool_choice(tool_choice)