You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running through the notebook, it's found that regardless we set the ToolConfig.FunctionCallingConfig.Mode to AUTO or ANY, the response from Gemini 1.5 Pro always responds back with two parts, one of text and the other of "function_call" as below:
This is not aligned with the forced function call which is supposed to respond back with only one parts of function_call.
In addition, as a side effect, in the step of getting params in the section of "Example: Using Forced Function Calling mode (ANY)" , we have to correct parts[0] to part[1] to make the notebook code cell work as shown below:
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
@JasperW01, thanks for letting us know and for the detailed bug report. I opened https://issuetracker.google.com/u/2/issues/340218113 and I put the details that you provided there so that the engineering team can take a deeper look. I'll leave this bug open until we get more information from the other bug report.
File Name
gemini/function-calling/forced_function_calling.ipynb
What happened?
When running through the notebook, it's found that regardless we set the ToolConfig.FunctionCallingConfig.Mode to AUTO or ANY, the response from Gemini 1.5 Pro always responds back with two parts, one of text and the other of "function_call" as below:
This is not aligned with the forced function call which is supposed to respond back with only one parts of function_call.
In addition, as a side effect, in the step of getting params in the section of "Example: Using Forced Function Calling mode (ANY)" , we have to correct parts[0] to part[1] to make the notebook code cell work as shown below:
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: