-
Notifications
You must be signed in to change notification settings - Fork 3k
[Bug]: Prompt Optmizer using invalid model #2076
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
Comments
Is there any timeline for the fix? Unfortunately, Gemini 1.5 Pro is used in the pipeline of the optimizer despite the model removal. I couldn't fix this myself since it seems that the usage of the model is hard coded in the docker image of the optimizer. Are there any workarounds? |
I also came across this. I thought it might be because it's retired (https://cloud.google.com/vertex-ai/generative-ai/docs/learn/model-versions#legacy-stable) but it's not. I also threw the stack trace into Gemini: Stack Trace Analysis: The provided stack trace indicates the error's origin and propagation through the application: Origin: The error surfaces within a Python application, seemingly part of an optimization process (optimize_main.par/..., instruction_optimizer.py). |
I have the same problem, setting the target_model to another gemini version did not help... |
@want-to-be-relaxed or @inardini can you look into this? |
Sorry for the inconvenience. The prompt optimizer was using Gemini 1.5 Pro as the optimizer model to rewrite the prompts. Since Gemini 1.5 Pro is deprecated, we just released a fix using a more recent model. |
File Name
https://github.com/GoogleCloudPlatform/generative-ai/blob/main/gemini/prompts/prompt_optimizer/vertex_ai_prompt_optimizer_ui.ipynb
What happened?
Looks like somewhere in the code is trying to use gemini 1.5 pro and referencing it through an invalid url.
Relevant log output
Detailed error: Error: The job failed: 404 Publisher Model `projects/XXXXX/locations/us-central1/publishers/google/models/gemini-1.5-pro-002` was not found or your project does not have access to it.
Code of Conduct
The text was updated successfully, but these errors were encountered: