fix: [Gemini] content filter errors handled properly #126
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/deploy-review
|
|
/deploy-review
|
|
/deploy-review
|
roman-romanov-o
approved these changes
Sep 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
chunk.candidatesmay be None or empty, when the response is blocked.Such a response will lead to out-of-bounds index runtime error when the adapter tries to access
chunk.candidates[0].So the fixes are the following:
chunk.candidates[0]before using it,chunk.prompt_feedbackand translate it tocontent_filterfinish reason.=====
For a test request to reproduce the blocking response - ask Gemini a question about a medium-size wiki-page referencing in the middle of it a sensitive topic.