Update to libraries-bom 26.20.0

[bvolpato]

Update google_cloud_platform_libraries_bom to 26.20.0.

Associated updates to gax_version, google_cloud_spanner_version, google_code_gson_version, and grpc_version following versions from https://mvnrepository.com/artifact/com.google.cloud/libraries-bom/26.20.0 (being indexed).

Attaching the effective pom generated with:

wget https://repo1.maven.org/maven2/com/google/cloud/libraries-bom/26.20.0/libraries-bom-26.20.0.pom

mvn help:effective-pom -f libraries-bom-26.20.0.pom

libraries-bom-26.20.0-effective-pom.txt

[codecov]

Codecov Report

Merging #27725 (48084c6) into master (af533fe) will decrease coverage by 0.01%.
The diff coverage is n/a.

❗ Current head 48084c6 differs from pull request most recent head 8de4f3c. Consider uploading reports for the commit 8de4f3c to get more accurate results

@@            Coverage Diff             @@
##           master   #27725      +/-   ##
==========================================
- Coverage   70.90%   70.89%   -0.01%     
==========================================
  Files         860      860              
  Lines      104633   104633              
==========================================
- Hits        74187    74177      -10     
- Misses      28893    28902       +9     
- Partials     1553     1554       +1     

Flag	Coverage Δ
python	80.00% <ø> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 7 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[github-actions]

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @kennknowles for label java.
R: @damccorm for label build.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[bvolpato]

Run Java PreCommit

[bvolpato]

Run Java_PVR_Flink_Batch PreCommit

[bvolpato]

Run Java_Pulsar_IO_Direct PreCommit

[bvolpato]

Run SQL PreCommit

[bvolpato]

Run SQL_Java17 PreCommit

[bvolpato]

Run SQL_Java11 PreCommit

[bvolpato]

Run Java PreCommit

[bvolpato]

Run SQL PreCommit

[bvolpato]

Run SQL_Java11 PreCommit

[bvolpato]

Run SQL_Java17 PreCommit

[bvolpato]

Investigating a few failures

[Abacn]

I see, Could not resolve com.google.guava:guava:32.1.1-jre.

[bvolpato]

Bumped version to be the same and giving it a try.

There's some weird handling of Guava that I am not familiar with. Both in terms of com.google.guava:listenablefuture and some handling to ignore any Android versions https://github.com/apache/beam/blob/master/buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugin.groovy#L1899-L1904

[bvolpato]

com.google.guava:guava:32.1.1-jre is valid, but it seems that it's being rejected by CI. Will need to take a more careful look

[bvolpato]

Found the reason: https://github.com/google/guava/releases/tag/v32.1.0#user-content-overlap

Going to try the suggested fix

[bvolpato]

Run Java_PVR_Flink_Docker PreCommit

[bvolpato]

Run GoPortable PreCommit

[bvolpato]

Run Python_PVR_Flink PreCommit

[bvolpato]

@mutianf @suztomo Are you familiar with the changes that are happening on Bigtable?

Seems like it's hitting a real regression

16:15:38 > Task :sdks:java:extensions:sql:test
16:15:38 
16:15:38 org.apache.beam.sdk.extensions.sql.meta.provider.bigtable.BigtableTableFlatTest > testSegementedInsert FAILED
16:15:38     java.lang.AssertionError at BigtableTableFlatTest.java:164
16:15:38         Caused by: java.lang.AssertionError at MatcherAssert.java:18
16:15:38 
16:15:58 715 tests completed, 1 failed, 8 skipped

readTransformWithSegment (proxy to .withMaxBufferElementCount(2)) is apparently dropping records.

[mutianf]

@bvolpato The test failure is caused from the emulator version bump. I'll look into it on Monday. I think we can revert the emulator version bump so the test can pass.

[bvolpato]

@bvolpato The test failure is caused from the emulator version bump. I'll look into it on Monday. I think we can revert the emulator version bump so the test can pass.

@mutianf Thanks, doing it! The bump was to match libraries-bom, but perhaps this is the reason why a very old version was pinned.

[bvolpato]

Run Spotless PreCommit

[bvolpato]

Run CommunityMetrics PreCommit

[bvolpato]

Run Spotless PreCommit

[bvolpato]

Oof, this was more complicated than I expected.

Guava introduced some complications https://github.com/google/guava/releases#user-content-duplicate-ListenableFuture

It went as far as hanging/infinite looping Gradle in the classpath resolution when importing Truth, which is built against 32.0.1-android. Excluding it for now, and can bump + remove TODOs when Truth 1.1.6 is out (bump was done already google/truth@3f00bfe).

Also, google-cloud-bigtable-emulator could not be updated to 0.162.1 (to match libraries-bom) due to a regression in a testcase. Bigtable team is taking a look at this.

@Abacn Can you have a new look since this changed quite a bit since the last time you reviewed? Thanks!

[Abacn]

Thanks for the quick fix!