-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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] safety settings Gemini broken #718
Comments
Failed to compile. :( |
I for nothing raised panic. |
https://discuss.ai.google.dev/t/flash-2-0-doesnt-respect-block-none-on-all-harm-categories/59352 found a fix instead of BLOCK_NONE we now must use OFF for Flash 2-0, but ONLY for Flash 2-0. if you send OFF with any other model you will get an error |
Wow, great find @darthalex2014 . What do you think could be a generic way of solving this in Big-AGI? |
You can now update to enjoy the "OFF" filtering. Will work on newer Gemini models, and may trip the older ones. I left both options in, and hopefully Gemini will converge quickly to one or another. |
Description
Everything was fine yesterday, but today the Censorship (SAFETY) Level switch for Gemini models is completely broken on v2-dev. It doesn't seem to affect anything anymore. All of my prompts that used to work now trigger an error "[Gemini Issue]: Generation stopped due to SAFETY: HARM_CATEGORY_...". (I verified by running an old fork of v2-dev, and it's working fine there.)
Device and browser
Mobile/Desktop, last v2-dev
Screenshots and more
No response
Willingness to Contribute
The text was updated successfully, but these errors were encountered: