Skip to content

fix(retail): add region tag for Python - Update remove fulfillment places #13466

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

rebeccaellis
Copy link
Contributor

Description

Fixes #415382524

Note: Before submitting a pull request, please open an issue for discussion if you are not associated with Google.

Checklist

@rebeccaellis rebeccaellis requested review from a team as code owners June 28, 2025 00:30
Copy link

snippet-bot bot commented Jun 28, 2025

Here is the summary of changes.

You are about to add 1 region tag.

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

  • Refresh this comment

@product-auto-label product-auto-label bot added api: retail Issues related to the Retail API API. samples Issues that are directly related to samples. labels Jun 28, 2025
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.

Summary of Changes

Hello @rebeccaellis, 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 enhances the existing remove_fulfillment_places Python sample for the Retail API by incorporating standard region tags. This change is primarily aimed at improving the sample's integration with automated documentation systems, making it easier to maintain and ensuring that the code snippets presented in documentation are always current and accurate.

Highlights

  • Documentation Improvement: Added [START] and [END] region tags to the remove_fulfillment_places.py sample. These tags are crucial for automated documentation generation, allowing specific code blocks to be easily extracted and displayed in official documentation.
  • Code Sample Consistency: The addition of these region tags ensures that the remove_fulfillment_places example adheres to the standard format for Google Cloud Python samples, improving consistency across the repository and facilitating better integration with documentation pipelines.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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
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 adds region tags to the remove_fulfillment_places.py script to create a new code sample. I've identified several issues in the existing code within the new region tags, including incorrect async usage and problematic error handling. I recommend that these issues be addressed before this sample is published in the documentation.

@@ -14,6 +14,8 @@

# Remove place IDs using Retail API.
#
# [START retail_remove_fulfillment_places]
Copy link
Contributor

Choose a reason for hiding this comment

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

high

The added region tag exposes the enclosed code as a public sample. The code within this new region tag has a few issues that should be addressed:

  1. The remove_places function is defined as async, but it doesn't use await for any asynchronous operations. The polling loop uses time.sleep(), which is synchronous and blocks the event loop. This function can be a regular synchronous function.

  2. The try...except GoogleAPICallError: pass block (lines 62-68) silently ignores potential failures from the remove_fulfillment_places operation. This can lead to subsequent steps running on an incorrect state and makes debugging very difficult. The operation's result should be properly checked for errors. The comment on line 61 is also misleading.

  3. The remove_places function also calls get_product and delete_product, which are teardown steps. This is a side effect that is not clear from the function name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: retail Issues related to the Retail API API. samples Issues that are directly related to samples.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants