Fix PreCommit Python

[aIbrahiim]

Please add a meaningful description for your change here

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[gemini-code-assist]

Summary of Changes

Hello @aIbrahiim, I'm Gemini Code Assist¹! 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 several issues impacting the stability and reliability of Python-related pre-commit checks and the portable runner. The changes include refining gRPC call parameters for job state management, refactoring unit test setup for YAML transforms, and improving the robustness of a cleanup script. These modifications collectively aim to ensure smoother execution of development workflows and more stable job processing.

Highlights

• Portable Runner Stability: Removed explicit timeouts from GetStateStream and GetMessageStream calls in the portable runner, which should improve stability and prevent premature timeouts during job state and message retrieval.
• YAML Transform Unit Test Refactoring: Introduced a dedicated pipeline creation function new_pipeline_expand_test for YAML transform unit tests and updated existing tests to use it, enhancing test clarity and isolation.
• Pre-commit Script Robustness: Modified the run_tox_cleanup.sh script to prevent failures when no files matching the cleanup patterns are found, by adding || true to the find -delete command.

🧠 New Feature in Public Preview: You can now enable Memory 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.

Changelog

• sdks/python/apache_beam/runners/portability/portable_runner.py
  • Removed timeout=self.timeout from GetStateStream and GetMessageStream calls.
• sdks/python/apache_beam/yaml/yaml_transform_unit_test.py
  • Added new_pipeline_expand_test function.
  • Updated several test_expand_pipeline methods to use new_pipeline_expand_test instead of new_pipeline.
• sdks/python/scripts/run_tox_cleanup.sh
  • Added || true to the find ... -delete command to prevent script failure when no files are found.

Activity

• No specific activity (comments, reviews, or progress updates) has been recorded for this pull request yet.

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. ↩