Skip to content
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

[Bug]: Forced Function Calling setting isn't different to the default AUTO setting #674

Open
1 task done
JasperW01 opened this issue May 12, 2024 · 1 comment
Open
1 task done
Assignees

Comments

@JasperW01
Copy link
Contributor

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:

image

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:

image

Relevant log output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@koverholt
Copy link
Member

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants