Make SubprocessServer shared cache purging idempotent#38455
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 subprocess servers would raise a ValueError during atexit shutdown if the cache had already been cleaned up. By making the purge operation idempotent and logging a warning instead of failing, the system now handles redundant cleanup calls gracefully, ensuring cleaner process termination. 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 modifies the purge method in subprocess_server.py to be idempotent, replacing a ValueError with a warning log when an owner is already purged. This change addresses issues where subprocesses are cleaned up multiple times during shutdown or test teardown. The test suite has been updated to reflect this behavior and includes a new test case for verification. Feedback was provided regarding the placement of the log message within a lock block, which could lead to performance issues or deadlocks.
|
Assigning reviewers: R: @jrmccluskey 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). |
Avoid raising ValueError during atexit shutdown when a cached subprocess server was already cleaned up earlier. Right now, such exception is already ignored (from the log below).
Example traceback (https://github.com/apache/beam/actions/runs/25705764624/job/75475412939):