Skip to content

Conversation

@parthea
Copy link
Contributor

@parthea parthea commented Jan 22, 2026

feat: update image to us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/python-librarian-generator@sha256:e7cc6823efb073a8a26e7cefdd869f12ec228abfbd2a44aa9a7eacc284023677

Generation failed for

  • google-cloud-logging

…prod/images-prod/python-librarian-generator@sha256:e7cc6823efb073a8a26e7cefdd869f12ec228abfbd2a44aa9a7eacc284023677
@parthea
Copy link
Contributor Author

parthea commented Jan 22, 2026

One or more libraries have failed to generate, please review PR description for a list of failed libraries.
For each failed library, open a ticket in that library’s repository and then you may resolve this comment and merge.

@product-auto-label product-auto-label bot added size: xl Pull request size is extra large. api: logging Issues related to the googleapis/python-logging API. labels Jan 22, 2026
@parthea parthea closed this Jan 22, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @parthea, 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 primarily focuses on updating the python-librarian-generator image. Concurrently, it removes all generated code and related infrastructure for the google-cloud-logging library, indicating that its generation process failed or it is being temporarily excluded from automated generation.

Highlights

  • Librarian Image Update: The python-librarian-generator image has been updated to a new SHA256 hash: e7cc6823efb073a8a26e7cefdd869f12ec228abfbd2a44aa9a7eacc284023677.
  • Removal of google-cloud-logging Components: All generated files, including clients, pagers, transports, and type definitions for the google-cloud-logging library (both v1 and v2), have been removed from the repository. This includes associated documentation, configuration files like mypy.ini, noxfile.py, and renovate.json, and generated sample snippets.
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
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 updates the image hash in .librarian/state.yaml and removes a large number of files related to google-cloud-logging and google-cloud-logging_v2 services, including documentation, configuration, and client code. The image update appears to be a routine maintenance task for the librarian tool. The extensive file removals suggest a significant refactoring or deprecation of the google-cloud-logging library components, potentially moving to a different structure or removing generated code. No specific code quality issues were identified in the remaining changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: logging Issues related to the googleapis/python-logging API. size: xl Pull request size is extra large.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant