Skip to content

Conversation

@feeblefakie
Copy link
Contributor

This is an automated backport of the following:

Please merge this PR after all checks have passed.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @feeblefakie, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request is an automated backport to the 3.17 branch, focusing on enhancing the clarity of error messages. It specifically addresses a minor but important correction in the ObjectStorageOperationChecker to ensure that when a blob column exceeds its allowed length, the resulting error message accurately displays the specific allowedLength rather than a generic maximum value. This improvement makes error reporting more precise and helpful for debugging.

Highlights

  • Error Message Correction: The pull request fixes an issue where the error message for OBJECT_STORAGE_BLOB_EXCEEDS_MAX_LENGTH_ALLOWED incorrectly displayed a generic Serializer.MAX_STRING_LENGTH_ALLOWED value.
  • Improved Error Reporting: The error message now accurately reflects the specific allowedLength for the blob column, providing more precise information when a length limit is exceeded.
  • Automated Backport: This change is an automated backport of an existing fix to the 3.17 branch, ensuring consistency across versions.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request is a backport that fixes an incorrect value in an error message. The change ensures that when a blob value exceeds the maximum allowed size, the error message displays the correct limit for the raw blob data, rather than the limit for the Base64-encoded string. This is a good fix that improves the clarity and usefulness of the error message for developers. The change is correct and I have no further feedback.

@brfrn169 brfrn169 merged commit 60733ec into 3.17 Dec 9, 2025
71 of 73 checks passed
@brfrn169 brfrn169 deleted the 3.17-pull-3264 branch December 9, 2025 00:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants