Backport to branch(3.10) : Fix status code handling

[feeblefakie]

This is an automated backport of the following:

• Original PR: Fix status code handling #323
• Backported commit: 8458852

Please merge this PR after all checks have passed.

[gemini-code-assist]

Summary of Changes

Hello @feeblefakie, I'm Gemini Code Assist¹! 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 aimed at refining the status code handling within the CommonService. The changes ensure that specific internal error conditions, such as invalid arguments and missing secrets, are accurately translated into their corresponding gRPC status codes. This enhancement improves the precision of error reporting, which is crucial for robust client-side error management and overall system reliability.

Highlights

• Status Code Mapping: The convert method in CommonService.java has been updated to correctly map the internal StatusCode.INVALID_ARGUMENT to the gRPC io.grpc.Status.INVALID_ARGUMENT.
• Secret Not Found Handling: The convert method now also correctly maps the internal StatusCode.SECRET_NOT_FOUND to the gRPC io.grpc.Status.NOT_FOUND.
• Backport: This pull request is an automated backport of a fix originally implemented in PR Fix status code handling #323 to the 3.10 branch.

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. ↩

[gemini-code-assist]

Code Review

This pull request is a backport of a fix for status code handling. The changes correctly add mappings for the INVALID_ARGUMENT and SECRET_NOT_FOUND status codes within the CommonService.convert method. This ensures they are translated to the appropriate gRPC statuses (INVALID_ARGUMENT and NOT_FOUND respectively) instead of falling through to the default UNKNOWN case. The changes are correct, minimal for a backport, and consistent with the existing code's style of ordering cases by their numeric value. I have reviewed the changes and found no issues.