-
Notifications
You must be signed in to change notification settings - Fork 22
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
Unparseable buffer saved to *llm-vertex-unparseable* #19
Comments
Thank you for the report! Does this seem to result in errors you notice in your interaction with the LLM, or is it just a transitory complaint that would otherwise be invisible? |
Gemini simply returns nothing except the "promptFeedback". I can reproduce with these query and safety setting. Request
Response
|
I see - so, if I understand the problem correctly - Gemini is responding correctly by refusing to answer the question, and we should throw an appropriate error to the user. I'll make this change. So, you'll still get an error, but a better one. |
Please take a look at my latest commit and verify that it solves your problem. Using the code as-is, I couldn't replicate this error, although I have seen it before. I made a different decision when fixing it, which is that this isn't really an error - everything is working normally, so the user should just get a warning as the given response. |
It seems that I cannot reproduce the "unparseable" error with 0.9.0.
|
@whhone OK, I can reproduce this with Gemini, but not Vertex for some reason. My fix seems to have worked. Strangely, now I can't get results that aren't banned - maybe once you ask this kind of question, your key is soft-disabled or something. I may have seen that before and I think it goes away after some time.
|
When trying to use Gemini, I see the error "Unparseable buffer saved to llm-vertex-unparseable" occasionally. Here is the content in the
*llm-vertex-unparseable*
:The text was updated successfully, but these errors were encountered: