Backport to branch(3.11) : 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 to the 3.11 branch, aimed at refining the error handling mechanism 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, which will lead to more precise error communication to clients.

Highlights

• Status Code Handling: Improved the mapping of internal status codes to gRPC status codes in CommonService.java to ensure more accurate error reporting.
• Error Code Mapping Expansion: Specifically, the internal INVALID_ARGUMENT status code is now correctly mapped to io.grpc.Status.INVALID_ARGUMENT, and SECRET_NOT_FOUND is mapped to io.grpc.Status.NOT_FOUND.

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 that correctly maps StatusCode.INVALID_ARGUMENT and StatusCode.SECRET_NOT_FOUND to their corresponding gRPC status codes. This is a good improvement as it ensures more specific error codes are returned to the client, instead of a generic INTERNAL error. The changes are correct and look good.