chore: librarian update image pull request: 20260205T214646Z#15532
chore: librarian update image pull request: 20260205T214646Z#15532
Conversation
…prod/images-prod/python-librarian-generator@sha256:f5426423676c75008c2135037e7b98f78cbb99f78b3c46fe043b6897be92d836
|
One or more libraries have failed to generate, please review PR description for a list of failed libraries. |
Summary of ChangesHello @ohmayr, 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 performs a routine update of the Python librarian generator image. Alongside this, it introduces a widespread refactoring of protobuf import statements to a more explicit Highlights
Changelog
Activity
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request appears to be an automated update from the librarian tool, refreshing the generator image and regenerating client libraries. The changes are mostly stylistic, such as updating import formats and serialization methods, which is fine. The identified recurring issue across many of the generated rest.py transport files regarding the use of bare except: clauses remains, as it is a valid concern not covered by the provided rules. All comments highlighting this issue have been retained with their original suggestions. This might be an issue in the generator itself that needs to be addressed.
| request_payload = type(request).to_json(request) | ||
| except: |
There was a problem hiding this comment.
Using a bare except: clause is discouraged as it catches all exceptions, including system-exiting ones like SystemExit or KeyboardInterrupt. It's better to catch a more specific exception, like Exception, to avoid unintentionally suppressing important errors.
| request_payload = type(request).to_json(request) | |
| except: | |
| request_payload = type(request).to_json(request) | |
| except Exception: |
| request_payload = type(request).to_json(request) | ||
| except: |
There was a problem hiding this comment.
Using a bare except: clause is discouraged as it catches all exceptions, including system-exiting ones like SystemExit or KeyboardInterrupt. It's better to catch a more specific exception, like Exception, to avoid unintentionally suppressing important errors.
| request_payload = type(request).to_json(request) | |
| except: | |
| request_payload = type(request).to_json(request) | |
| except Exception: |
| request_payload = type(request).to_json(request) | ||
| except: |
There was a problem hiding this comment.
Using a bare except: clause is discouraged as it catches all exceptions, including system-exiting ones like SystemExit or KeyboardInterrupt. It's better to catch a more specific exception, like Exception, to avoid unintentionally suppressing important errors.
| request_payload = type(request).to_json(request) | |
| except: | |
| request_payload = type(request).to_json(request) | |
| except Exception: |
| request_payload = type(request).to_json(request) | ||
| except: |
There was a problem hiding this comment.
Using a bare except: clause is discouraged as it catches all exceptions, including system-exiting ones like SystemExit or KeyboardInterrupt. It's better to catch a more specific exception, like Exception, to avoid unintentionally suppressing important errors.
| request_payload = type(request).to_json(request) | |
| except: | |
| request_payload = type(request).to_json(request) | |
| except Exception: |
| request_payload = type(request).to_json(request) | ||
| except: |
There was a problem hiding this comment.
Using a bare except: clause is discouraged as it catches all exceptions, including system-exiting ones like SystemExit or KeyboardInterrupt. It's better to catch a more specific exception, like Exception, to avoid unintentionally suppressing important errors.
| request_payload = type(request).to_json(request) | |
| except: | |
| request_payload = type(request).to_json(request) | |
| except Exception: |
| request_payload = type(request).to_json(request) | ||
| except: |
There was a problem hiding this comment.
Using a bare except: clause is discouraged as it catches all exceptions, including system-exiting ones like SystemExit or KeyboardInterrupt. It's better to catch a more specific exception, like Exception, to avoid unintentionally suppressing important errors.
| request_payload = type(request).to_json(request) | |
| except: | |
| request_payload = type(request).to_json(request) | |
| except Exception: |
| request_payload = type(request).to_json(request) | ||
| except: |
There was a problem hiding this comment.
Using a bare except: clause is discouraged as it catches all exceptions, including system-exiting ones like SystemExit or KeyboardInterrupt. It's better to catch a more specific exception, like Exception, to avoid unintentionally suppressing important errors.
| request_payload = type(request).to_json(request) | |
| except: | |
| request_payload = type(request).to_json(request) | |
| except Exception: |
| request_payload = type(request).to_json(request) | ||
| except: |
There was a problem hiding this comment.
Using a bare except: clause is discouraged as it catches all exceptions, including system-exiting ones like SystemExit or KeyboardInterrupt. It's better to catch a more specific exception, like Exception, to avoid unintentionally suppressing important errors.
| request_payload = type(request).to_json(request) | |
| except: | |
| request_payload = type(request).to_json(request) | |
| except Exception: |
| request_payload = type(request).to_json(request) | ||
| except: |
There was a problem hiding this comment.
Using a bare except: clause is discouraged as it catches all exceptions, including system-exiting ones like SystemExit or KeyboardInterrupt. It's better to catch a more specific exception, like Exception, to avoid unintentionally suppressing important errors.
| request_payload = type(request).to_json(request) | |
| except: | |
| request_payload = type(request).to_json(request) | |
| except Exception: |
| request_payload = type(request).to_json(request) | ||
| except: |
There was a problem hiding this comment.
Using a bare except: clause is discouraged as it catches all exceptions, including system-exiting ones like SystemExit or KeyboardInterrupt. It's better to catch a more specific exception, like Exception, to avoid unintentionally suppressing important errors.
| request_payload = type(request).to_json(request) | |
| except: | |
| request_payload = type(request).to_json(request) | |
| except Exception: |
feat: update image to us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/python-librarian-generator@sha256:f5426423676c75008c2135037e7b98f78cbb99f78b3c46fe043b6897be92d836
Generation failed for