Skip to content

Fix annotations on methods that return Stream<@Nullable Object[]> - #6213

Merged
mpkorstanje merged 1 commit into
junit-team:mainfrom
msridhar:array-stream-nullable-contents-fixes
Oct 28, 2026
Merged

mpkorstanje merged 1 commit into
junit-team:mainfrom
msridhar:array-stream-nullable-contents-fixes

Conversation

@msridhar

Copy link
Copy Markdown
Contributor

NullAway will warn on all of these cases once uber/NullAway#2080 lands. Arguments::get references a method that returns @Nullable Object[], so all the return types of these methods should be Stream<@Nullable Object[]>. No logic changes, just annotations and formatting.

Signed-off-by: Manu Sridharan <msridhar@gmail.com>
@testlens-app

testlens-app Bot commented Oct 28, 2026

Copy link
Copy Markdown

✅ All tests passed ✅

🏷️ Commit: 74338c7
▶️ Tests: 23108 executed
⚪️ Checks: 16/16 completed


Learn more about TestLens at testlens.app/docs.

@mpkorstanje mpkorstanje left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Cheers!

@mpkorstanje
mpkorstanje merged commit 778cef5 into junit-team:main Oct 28, 2026
20 checks passed
@msridhar
msridhar deleted the array-stream-nullable-contents-fixes branch October 28, 2026 16:53
marcphilipp pushed a commit that referenced this pull request Oct 29, 2026
Previously, NullAway warnings blocked the build due to `-Werror`.  By 
setting NullAway to error directly, more warnings get emitted in a 
single build (due to google/error-prone#4546).
I noticed this while working on #6213.

Signed-off-by: Manu Sridharan <msridhar@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants