-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Fix missing tool call id if tool call index >0 in streaming tool call output. #7049
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
Conversation
… output. Signed-off-by: 许文卿 <xwq391974@alibaba-inc.com>
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.
Summary of Changes
Hello @Xu-Wenqing, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request addresses a specific bug in the streaming API response for tool calls. Previously, only the very first tool call object in the stream would receive an id
. This change updates the streaming logic to assign a unique id
whenever a new tool call object is encountered, identified by a change in the tool_index
, thus fixing the reported issue.
Highlights
- Bug Fix: Resolved an issue where
tool_call.id
was not included in streaming output for tool calls with an index greater than 0. - Streaming Tool Calls: Modified the logic within the streaming response generation to correctly identify the start of a new tool call object based on its index, ensuring a unique ID is generated for each distinct tool call in the stream.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configureGemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
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.
Code Review
This pull request effectively fixes a bug where tool call IDs were missing for subsequent tool calls in streaming outputs. The change from using a tool_call_first
flag to tracking tool_index_previous
and tool_index_current
is a clear and correct solution. The updated logic ensures that a unique ID is generated for the first chunk of each new tool call, while subsequent chunks of the same tool call correctly have a null
ID, which aligns with standard API behavior for streaming tool calls.
… output. Signed-off-by: 许文卿 <xwq391974@alibaba-inc.com>
… output. Signed-off-by: 许文卿 <xwq391974@alibaba-inc.com>
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.
LGTM. Thanks for fixing this @Xu-Wenqing
Can you add a screenshot of a local test if possible? Maybe reuse the script in the issue
@CatherineSue Added script and streaming return in PR description. |
… output. (sgl-project#7049) Signed-off-by: 许文卿 <xwq391974@alibaba-inc.com>
… output. (sgl-project#7049) Signed-off-by: 许文卿 <xwq391974@alibaba-inc.com>
Motivation
Fix this: #7048
Modifications
Test Script:
Test Result:
Checklist