Skip to content

Conversation

@amanda-tarafa
Copy link
Contributor

No description provided.

@amanda-tarafa amanda-tarafa requested review from a team as code owners January 21, 2026 23:35
@product-auto-label product-auto-label bot added the api: storage Issues related to the Cloud Storage API. label Jan 21, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @amanda-tarafa, 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 focuses on adapting the Google Cloud Storage C# client's integration tests to a new CI environment. It primarily involves temporarily skipping tests that are currently failing or unstable in the new setup, alongside minor refactorings to test data and IAM policy definitions to enhance test robustness and clarity. Additionally, a new project reference was added to the solution.

Highlights

  • Test Skipping for New CI: Several integration tests across HmacKeysTest, NormalizationTest, PublicAccessPreventionTest, StorageClientSnippets, and UrlSignerSnippets have been temporarily skipped, referencing specific bug IDs (b/477663109, b/477619774, b/477676781), to address compatibility issues with the new CI environment.
  • Test Data Refactoring: Hardcoded string literals for gzipped object names and content in DownloadObjectTest have been replaced with constants defined in StorageFixture for improved maintainability and consistency.
  • IAM Policy Member Update: Test and snippet code related to IAM policies in PublicAccessPreventionTest and StorageClientSnippets has been updated to use allUsers instead of domain:google.com for defining policy members.
  • Solution File Update: A new project reference for Google.Cloud.PubSub.V1 has been added to the Google.Cloud.Storage.V1.sln solution file.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

@amanda-tarafa
Copy link
Contributor Author

Reviewing one commit at a time is best.

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 primarily focuses on fixing and skipping integration tests for the Storage client library to improve CI stability. The changes include skipping several tests with references to internal bug reports, which is a reasonable approach for flaky tests. Additionally, some hardcoded strings in DownloadObjectTest have been refactored into constants, which improves code quality. However, I've identified a few issues that need attention. There's a potential bug in the value of a new constant that could cause tests to fail. I also noticed a confusing data change in a skipped test case in NormalizationTest.cs. Finally, an unrelated project reference has been added to the solution file, which seems out of scope for this PR. My detailed comments address these points.

Copy link
Contributor

@robertvoinescu-work robertvoinescu-work left a comment

Choose a reason for hiding this comment

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

LGTM: Just one NIT

// Normalization Form C: a single character for e-acute.
// URL should end with Caf%C3%A9
[InlineData("Caf\u00e9", "Normalization Form C")]
// Normalization Form D: an ASCII e followed by U+0301 combining character
Copy link
Contributor

Choose a reason for hiding this comment

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

This comment also needs to be updated to match the new data.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done, thanks.

When we migrated CI, the new gZipped object that was created has cased "Hello World". It's easier to change the tests than to change the object being created via Terraform.
See b/477676781.

Note these were further broken in a previous attempt to fix them at googleapis#14741 and googleapis#14744
@amanda-tarafa
Copy link
Contributor Author

/gemini review

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 primarily focuses on fixing and skipping tests to stabilize the CI environment. The changes include refactoring hardcoded values in DownloadObjectTest to use constants, which also corrects the expected content of a gzipped file. Several tests across different files (HmacKeysTest, NormalizationTest, PublicAccessPreventionTest, StorageClientSnippets, UrlSignerSnippets) are skipped with corresponding bug tracker IDs. Additionally, some test data and code comments have been updated for correctness, such as changing a member from a specific domain to allUsers.

My main feedback is regarding a change in the solution file that seems out of scope. Otherwise, the changes look good and contribute to improving the test suite's stability and maintainability.

@amanda-tarafa
Copy link
Contributor Author

(closed by accident)

@amanda-tarafa
Copy link
Contributor Author

/gemini review

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 primarily focuses on updating and skipping tests for a new CI environment. The changes include refactoring hardcoded values to constants and disabling tests that are currently failing. My review has identified a potential issue with a case-sensitivity change in test data that could lead to test failures, and an unrelated project reference that seems to have been added to the solution file accidentally. Overall, the changes are straightforward, but these two points warrant attention.

@amanda-tarafa amanda-tarafa merged commit 0e0ff75 into googleapis:main Jan 22, 2026
23 checks passed
@amanda-tarafa amanda-tarafa deleted the storage-ci branch January 22, 2026 00:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: storage Issues related to the Cloud Storage API.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants