Backport to branch(3.12) : 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 backports a critical fix to the 3.12 branch, enhancing the system's error handling by ensuring that specific internal status codes, such as INVALID_ARGUMENT and SECRET_NOT_FOUND, are accurately translated into their corresponding gRPC status codes. This improves the consistency and clarity of error responses for clients interacting with the service.

Highlights

• Status Code Mapping: The internal INVALID_ARGUMENT status code is now correctly mapped to io.grpc.Status.INVALID_ARGUMENT.
• Secret Not Found Handling: The internal SECRET_NOT_FOUND status code is now correctly mapped to io.grpc.Status.NOT_FOUND.
• Automated Backport: This pull request is an automated backport of a previous fix, ensuring consistent error handling in the 3.12 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 correctly adds gRPC status code mappings for INVALID_ARGUMENT and SECRET_NOT_FOUND. The change is functionally correct. I have added one suggestion to refactor the convert method using a Map instead of a switch statement. This would improve the code's readability and maintainability as more status codes are added in the future.