[DO NOT MERGE] Validate Beam 2.71.0rc3

[damccorm]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @damccorm, 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 focuses on updating the project's dependencies to a newer release candidate of Apache Beam. It involves modifying the Maven build configuration to point to the new Beam version and repository, as well as updating numerous Python dependency files to reflect the new Beam version and introduce several new related Python packages. The changes ensure compatibility and leverage the latest features or fixes from the updated Beam version and its ecosystem.

Highlights

• Apache Beam Version Update: The core Apache Beam version has been updated from 2.70.0 to 2.71.0 in the pom.xml file, and Python dependencies for Apache Beam have been updated to 2.71.0rc2 across various requirements.txt files.
• Maven Repository Configuration: A new Apache Beam Maven repository URL (https://repository.apache.org/content/repositories/orgapachebeam-1421) has been added to pom.xml to fetch the updated Beam artifacts.
• Build Profile Activation Logic: The activation logic for the validateCandidate Maven profile in pom.xml has been changed from activeByDefault to a JDK version range [1.).
• Python Dependency Updates: Several Python dependencies, including beartype (from 0.21.0 to 0.22.9) and numpy (from 2.2.6 to 2.4.0), have been updated, along with their corresponding SHA256 hashes for integrity verification.
• New Python Dependencies Introduced: New Python packages such as betterproto, envoy-data-plane, grpclib, h2, hpack, and hyperframe have been added to the requirements.txt files, indicating new functionalities or updated dependency trees.

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 50.84%. Comparing base (200724c) to head (5f4764d).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #3222      +/-   ##
============================================
- Coverage     50.84%   50.84%   -0.01%     
- Complexity     5135     5512     +377     
============================================
  Files           976      976              
  Lines         60106    60106              
  Branches       6575     6575              
============================================
- Hits          30562    30561       -1     
- Misses        27391    27395       +4     
+ Partials       2153     2150       -3     

Components	Coverage Δ
spanner-templates	70.96% <ø> (-0.02%)	⬇️
spanner-import-export	68.86% <ø> (-0.02%)	⬇️
spanner-live-forward-migration	80.12% <ø> (+0.01%)	⬆️
spanner-live-reverse-replication	77.72% <ø> (-0.04%)	⬇️
spanner-bulk-migration	88.45% <ø> (+0.01%)	⬆️
see 8 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[damccorm]

This is running into the same problems as the last rc :( I'm not sure why yet. I did confirm that https://repository.apache.org/content/repositories/orgapachebeam-1421/org/apache/beam/beam-sdks-java-io-google-cloud-platform/2.71.0/ should contain the correct Spanner version...

[damccorm]

mvn help:effective-pom -Dartifact=org.apache.beam:beam-sdks-java-google-cloud-platform-bom:2.71.0 still shows

      <dependency>
        <groupId>com.google.cloud</groupId>
        <artifactId>google-cloud-spanner</artifactId>
        <version>6.105.0</version>
      </dependency>

which is probably the issue. I'll dig in more here.