Skip to content

Conversation

shivaspeaks
Copy link
Member

@shivaspeaks shivaspeaks commented Sep 30, 2025

Internal: cl/813142534

@shivaspeaks shivaspeaks marked this pull request as ready for review September 30, 2025 13:59
@shivaspeaks shivaspeaks requested a review from ejona86 September 30, 2025 13:59
Copy link
Member

@ejona86 ejona86 left a comment

Choose a reason for hiding this comment

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

This sort of thing is public as well: https://errorprone.info/bugpattern/CheckReturnValue

@shivaspeaks
Copy link
Member Author

shivaspeaks commented Sep 30, 2025

So this workaround is fine, but how wrong is to check non-null against a constructor-returned object? I know that's not right programatically but since its a workaround...

@ejona86
Copy link
Member

ejona86 commented Sep 30, 2025

but how wrong is to check non-null against a constructor-returned object

I would easily delete that code if I was updating things in the test. The purpose is not clear, as it is testing something impossible.

@shivaspeaks shivaspeaks added the kokoro:force-run Add this label to a PR to tell Kokoro to re-run all tests. Not generally necessary label Sep 30, 2025
@grpc-kokoro grpc-kokoro removed the kokoro:force-run Add this label to a PR to tell Kokoro to re-run all tests. Not generally necessary label Sep 30, 2025
@shivaspeaks shivaspeaks changed the title xds: Update XdsTrustManagerFactoryTest.java xds: Use unused variable to ignore the return value Oct 1, 2025
@shivaspeaks shivaspeaks merged commit 7d5749f into grpc:master Oct 1, 2025
18 of 23 checks passed
@shivaspeaks shivaspeaks deleted the main branch October 1, 2025 06:07
AgraVator pushed a commit to AgraVator/grpc-java that referenced this pull request Oct 6, 2025
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.

3 participants