-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
fix(provider): fall back when upstream omits tool_call id #9681
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
LIKIQ
wants to merge
1
commit into
AstrBotDevs:master
Choose a base branch
from
LIKIQ:fix/tool-call-missing-id
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
issue (complexity): Consider extracting tool_call index normalization and ID fallback into dedicated helper methods to keep the hot-path streaming and parsing logic focused and easier to read.
The new logic is functionally solid, but both index normalization and ID fallback are tightly inlined into hot paths. You can reduce cognitive load by pushing these concerns into small helpers that encapsulate state, while keeping behavior identical.
1. Extract tool_call index normalization into a helper
Instead of mutating
tool_call_index_mapinline inside the streaming loop, encapsulate the mapping in a tiny helper or state object:Then
_query_streambecomes:This keeps the streaming loop focused on “what” is happening, and hides the “how” of normalization.
2. Centralize tool_call id normalization
You’ve added
fallback_tool_call_id, and the reviewer notesLLMResponse._safe_tool_call_idalready exists. Right now,_parse_openai_completionhas its own ID normalization; you can delegate ID normalization toLLMResponseand avoid duplicating responsibility.For example, keep
_parse_openai_completioncollecting raw IDs (includingNone), and letLLMResponsenormalize when constructing the final response:Then in
LLMResponse:Call
llm_response.finalize_tool_calls()at the end of_parse_openai_completion. This keeps all ID fallback logic (including alignment with list index and extra_content mapping) in one place, and removes the need for inlinegetattr+ warning +fallback_tool_call_idin_parse_openai_completion, while preserving the current behavior.