Skip to content

test(bigtable): resolve NullArgumentForNonNullParameter error in MaybePointWriteCallableTest - #14179

Merged
lqiu96 merged 1 commit into
mainfrom
fix-14174-bigtable-native-compile
Aug 24, 2026
Merged

test(bigtable): resolve NullArgumentForNonNullParameter error in MaybePointWriteCallableTest#14179
lqiu96 merged 1 commit into
mainfrom
fix-14174-bigtable-native-compile

Conversation

@lqiu96

@lqiu96 lqiu96 commented Aug 24, 2026

Copy link
Copy Markdown
Member

Fixes #14174

Problem

During GraalVM native presubmit CI compilation under JDK 21 with ErrorProne enabled, MaybePointWriteCallableTest.java failed with:
[NullArgumentForNonNullParameter] at line 59: assertThat((Object) future.get()).isNull().

  • future.get() on ApiFuture<Void> evaluates to null (or throws an exception).
  • ErrorProne failed to resolve Truth's @Nullable parameter annotation on assertThat(@Nullable Object actual) inside the @NullMarked package when reading bytecode in CI, flagging passing a known-null value.

Solution

Replace assertThat((Object) future.get()).isNull() with direct future.get() to verify successful completion without exception.

@lqiu96
lqiu96 requested review from a team as code owners August 24, 2026 20:26

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates MaybePointWriteCallableTest.java by simplifying an assertion on a future's result in singleEntry_routesToPointWriter and adding an assertion to verify that the returned future is the same instance as the classic response in multipleEntries_fallsThroughToClassic. I have no feedback to provide.

@lqiu96 lqiu96 changed the title fix(bigtable): resolve NullArgumentForNonNullParameter error in MaybePointWriteCallableTest test(bigtable): resolve NullArgumentForNonNullParameter error in MaybePointWriteCallableTest Aug 24, 2026
…PointWriteCallableTest

Fixes #14174

Replace redundant Truth assertThat((Object) future.get()).isNull() on ApiFuture<Void>
with direct future.get() to avoid ErrorProne NullArgumentForNonNullParameter false-positives
under GraalVM / JDK 21 CI.
@lqiu96
lqiu96 force-pushed the fix-14174-bigtable-native-compile branch from 710d7f3 to 14d14c2 Compare August 24, 2026 20:30
@lqiu96
lqiu96 enabled auto-merge (squash) August 24, 2026 21:16
@lqiu96
lqiu96 merged commit de926bd into main Aug 24, 2026
210 checks passed
@lqiu96
lqiu96 deleted the fix-14174-bigtable-native-compile branch August 24, 2026 21:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BigTable Compilation Issue GraalVM CI

2 participants