Skip to content

Conversation

@bajajneha27
Copy link
Contributor

No description provided.

@bajajneha27 bajajneha27 requested review from a team as code owners November 27, 2025 11:16
@product-auto-label product-auto-label bot added the api: storage Issues related to the Cloud Storage API. label Nov 27, 2025
@gemini-code-assist
Copy link

Summary of Changes

Hello @bajajneha27, 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 introduces minor refinements to the storage client library. It includes a small performance optimization in how unreachable bucket names are added to a vector during response parsing, and a documentation correction to improve clarity regarding the ReturnPartialSuccess option.

Highlights

  • Performance Optimization: Replaced emplace_back with push_back when adding std::string elements to the unreachable vector in ListBucketsResponse parsing, aiming for minor performance improvements.
  • Documentation Correction: Updated a comment in well_known_parameters.h to accurately describe the ReturnPartialSuccess option, changing 'unreachable regions' to 'unreachable resources'.
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

@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 makes a minor performance improvement by using push_back instead of emplace_back for temporary objects, which is consistent with the Google C++ style guide. It also corrects a comment in well_known_parameters.h. I've suggested a further performance improvement in bucket_requests.cc by reserving memory for the vector to avoid reallocations.

Comment on lines 247 to 249
for (auto const& kv : json["unreachable"].items()) {
result.unreachable.emplace_back(kv.value().get<std::string>());
result.unreachable.push_back(kv.value().get<std::string>());
}

Choose a reason for hiding this comment

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

medium

Since this change is for performance, we can further improve it by reserving space in the vector before populating it. This avoids multiple reallocations if there are many unreachable locations. We can also simplify the loop by iterating directly over the JSON array elements instead of using .items().

    auto const& unreachable = json["unreachable"];
    result.unreachable.reserve(unreachable.size());
    for (auto const& location : unreachable) {
      result.unreachable.push_back(location.get<std::string>());
    }

@codecov
Copy link

codecov bot commented Nov 27, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.94%. Comparing base (a202418) to head (91b670f).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #15803      +/-   ##
==========================================
- Coverage   92.95%   92.94%   -0.01%     
==========================================
  Files        2458     2458              
  Lines      227548   227548              
==========================================
- Hits       211518   211499      -19     
- Misses      16030    16049      +19     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@bajajneha27 bajajneha27 merged commit bf93649 into googleapis:main Dec 2, 2025
63 of 66 checks passed
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.

3 participants