FIX: gemini tool call hanging #3898
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
The response_to_streaming_message function in the OpenAI format provider was not returning tool call messages to the stream when AI providers send complete tool calls in a single chunk with finish_reason: "tool_calls".
Root Cause: The original logic assumed all tool calls would be streamed across multiple chunks (like OpenAI's behavior) and always entered a loop to wait for additional tool call data. When providers like Gemini send complete tool calls in one chunk, the function would:
4.Break out of the entire function without yielding the tool call message
This resulted in tool calls being processed but never returned to the caller, causing streaming responses to appear empty.
Fix
Added a check to detect when tool calls are already complete in the initial chunk