-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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]: grounding notebook does not work with gemini-2.0-flash-exp #1535
Comments
This is working as expected. Gemini 2.0 only works with the updated SDK, which this notebook is not using. Refer to this notebook to see how to use Gemini 2.0 with Grounding. https://github.com/GoogleCloudPlatform/generative-ai/blob/main/gemini/getting-started/intro_gemini_2_0_flash.ipynb I'll make a PR to add a notice to these notebooks. |
Thanks for this. As a heads up for my fellow test pilots, the grounding is in intro_gemini_2_0_flash.ipynb but you have to go down into the notebook Cell titled Google Search . The calls worked for me upon getting synched to the examples provided. As of 27 Dec 2024 it does not appear that the intro-grounding-gemini.ipynb is set up for Gemini 2.0. |
@holtskinner so we only need to add the
But when uncommenting those lines: "1 validation error for googlesearch dynamic_retrieval_config extra inputs are not permitted [type=extra_forbidden, input_value=dynamicretrievalconfig(mo..., dynamic_threshold=0.0), input_type=dynamicretrievalconfig] for further information visit https://errors.pydantic.dev/2.10/v/extra_forbidden " My application confabulates URLs like crazy without turning the threshold to 0. Details on request. |
File Name
gemini/grounding /intro-grounding-gemini.ipynb
What happened?
(hello from a Xoogler)
If you run the initial code from the notebook using
An error is produced. See below. Switching back to flash-1.5 works just fine.
Noting that this is an issue in google-cloud-aiplatform. See googleapis/python-aiplatform#4779 but if it requires notebook changes once resolved, including an issue report here.
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: