[TEST - DO NOT MERGE] CI for Apache Beam 2.55.1 with spark version 3.5.3

[DoctorCatCodes]

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 @DoctorCatCodes, 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 serves as a test run for continuous integration, specifically validating the compatibility and build process for Apache Beam version 2.55.1 with Spark 3.5.3. It encompasses updates to various build configurations and dependency versions to align with these target versions. Key changes include refactoring of internal Dataflow worker logging and state caching mechanisms, enhancements to Beam's version comparison utility, and the introduction of compatibility logic for BigQueryIO transforms during pipeline upgrades. Additionally, it addresses environment resolution in the Python Fn Runner and temporarily disables the Gradle build cache.

Highlights

• Dataflow Container Version Update: The Dataflow container versions used in runners/google-cloud-dataflow-java/build.gradle have been updated from a beam-master snapshot to 2.55.1, aligning with the PR's stated target Beam version.
• Spark Version Update: The default Spark version for compatibility tests in runners/spark/3/build.gradle has been updated from 3.5.0 to 3.5.3, reflecting the PR's focus on this specific Spark version.
• Dataflow Worker Logging and State Tracking Refactoring: Significant refactoring of logging and execution state tracking in Dataflow worker components (ExecutionStateTracker.java, DataflowExecutionContext.java, DataflowOperationContext.java) has occurred. This includes removing redundant bundle lull reporting, consolidating stack trace utilities, and integrating StackTraceUtil functionality directly into DataflowOperationContext.java.
• Dataflow Worker State Caching Improvement: The calculation of cached size for state objects in WindmillBag.java, WindmillValue.java, and WindmillWatermarkHold.java has been adjusted to include the stateKey.size(), likely improving the accuracy of cache weight management.
• New Beam Version Comparison Utility: A new utility method TransformUpgrader.compareVersions has been added to sdks/java/core/src/main/java/org/apache/beam/sdk/util/construction/TransformUpgrader.java for robust comparison of Beam version strings, including handling of patch and suffix components.
• BigQueryIO Upgrade Compatibility: Compatibility logic has been introduced in BigQueryIOTranslation.java to handle bad_record_router and bad_record_error_handler when upgrading pipelines from Beam versions older than 2.55.0, utilizing the new version comparison utility to ensure smooth transitions.
• Python Fn Runner Environment Resolution: The Python Fn Runner (fn_runner.py) now includes a resolve_any_environments method to properly handle AnyOf environments, ensuring optimal selection of execution environments (e.g., Docker, external) during pipeline execution.
• Gradle Build Cache Disablement: The Gradle build cache has been temporarily disabled in settings.gradle.kts, indicating ongoing maintenance or issues with the remote cache infrastructure.
• Go Module Integration: New Go module files (go.mod, go.sum) have been added, suggesting the introduction or expansion of Go-related components or CI processes within the project.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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