-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NP_NONNULL_PARAM_VIOLATION false-positive #484
Comments
KengoTODA
added a commit
that referenced
this issue
Oct 31, 2017
KengoTODA
added a commit
that referenced
this issue
Oct 31, 2017
KengoTODA
added a commit
that referenced
this issue
Oct 31, 2017
henrik242
pushed a commit
that referenced
this issue
Nov 3, 2017
henrik242
pushed a commit
that referenced
this issue
Nov 3, 2017
Hi all, may be I'm wrong, but I don't see commits on the master. Was this only fixed on 3.1.0 branch? We should apply it to 4.0 too. |
Arrgh, there is no way to put the issue to two milestones? OMG. |
iloveeclipse
added a commit
to iloveeclipse/spotbugs
that referenced
this issue
Jan 5, 2018
This fixes issues spotbugs#519, spotbugs#478, spotbugs#484 and spotbugs#516
Which version of maven plugin contains this fix? |
Same issue with |
This was referenced Dec 30, 2020
KengoTODA
pushed a commit
that referenced
this issue
Jan 5, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just hit this, Googled and found:
https://sourceforge.net/p/findbugs/bugs/1403/
I have the same issue -
future.complete(null)
is giving aNP_NONNULL_PARAM_VIOLATION
while it shouldn't.P.S. SpotBugs 3.1.0.
The text was updated successfully, but these errors were encountered: