Fix interactive environment clean up failure at atexit.#38526
Conversation
Summary of ChangesHello, 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 addresses an issue where interactive environment cleanup failures during the atexit phase caused noisy and unnecessary exceptions in test logs. By catching these exceptions and logging them as warnings, the cleanup process becomes more resilient and the test output is significantly cleaner. Highlights
New Features🧠 You can now enable Memory (public preview) 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 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 the 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 counterproductive. 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. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces error handling and logging to the cleanup method of the CacheManager to ensure that failures during cache deletion are caught and logged rather than causing a crash. While the logging implementation is sound, the reviewer identified that moving GCP-related imports to the top level introduces a hard dependency on the google-cloud-storage library, which would cause ImportError for users without GCP dependencies installed. The feedback recommends reverting these to local imports within the cleanup method to maintain the optional nature of GCP support in the Beam SDK.
|
Assigning reviewers: R: @claudevdm for label python. Note: If you would like to opt out of this review, comment Available commands:
The PR bot will only process comments in the main thread (not review comments). |
|
The failure of "PreCommit Python PVR Flink" exists in master branch as well, so it is irrelevant to the change made here. |
The exception occurs in test clean up only and is harmless. Changing it to a warning message and make the test log cleaner.
https://github.com/apache/beam/actions/runs/26003104622/job/76429819073