Fix/block base64#223
Merged
Merged
Conversation
VitjanZ
force-pushed
the
fix/block_base64
branch
from
9c922fe to
f224352
Compare
VitjanZ
force-pushed
the
fix/block_base64
branch
from
f224352 to
59781ba
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Added a check for large base64 encoded blocks in the specs and reference files. If such a block is detected the render is finished and the user is informed of the reason. We do not support including these types of files currently and adding them as text-based reference files should also not be supported.
Requests that include larger base64 encoded blocks actually get rejected by Gemini API.
This pull request is to address the following issue: https://codeplain.sentry.io/issues/7551213541/?project=4510794036674560