Conversation
Need to create a new tagThe following modules have changes and may need version updates:
|
hi-pender
reviewed
Mar 6, 2026
hi-pender
approved these changes
Mar 6, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What type of PR is this?
fix
Check the PR title.
(Optional) Translate the PR title into Chinese.
fix(gemini): assistant message 通过 convSchemaMessage 还原为 candidate parts 时,tool call part 所在位置问题
(Optional) More detailed description for this PR(en: English/zh: Chinese).
en: This PR fixes the order of tool call parts in the convSchemaMessage function. Previously, tool call parts were added at the beginning of the content parts list, which could cause issues with Gemini API expectations. Now tool call parts are properly placed after media parts (when using AssistantGenMultiContent ) or after text parts (when using Content ). This ensures compatibility with Gemini's expected message format.
zh(optional): 此 PR 修复了 convSchemaMessage 函数中 tool call 部分的顺序问题。之前,tool call 部分被添加到 content parts 列表的开头,这可能导致与 Gemini API 期望不兼容的问题。现在,tool call 部分被正确地放置在 media 部分之后(当使用 AssistantGenMultiContent 时)或 text 部分之后(当使用 Content 时)。这确保了与 Gemini 期望的消息格式的兼容性。
(Optional) Which issue(s) this PR fixes:
(optional) The PR that updates user documentation: