-
Notifications
You must be signed in to change notification settings - Fork 578
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
java.lang.IllegalArgumentException: true #893
Comments
I am seeing this error also on the following kind of code. There are similarities to the previously posted code: a Boolean variable being updated with the &= operator in a loop. @Override
public boolean isEditorEnabled(AbstractPaCoModel<P> model) {
Boolean result = true;
for(PaCoParameterValuePair<P> pair : this.parameterValuePairs)
{
//if the corresponding linked editor is disabled, then disable this one too!
if(pair.getParameter().getEditorEnabler()!= null
&& !pair.getParameter().getEditorEnabler().isEditorEnabled(model)) {
return false;
}
boolean isValueMatching = false;
Object objectValue = pair.getValue();
BOPaCoParameter<P> boParameter = model.getParameter(pair.getParameter());
if(objectValue == null || boParameter == null) {
return true;
}
if(objectValue instanceof IPaCoParameterValueEnum)
{
isValueMatching = ((IPaCoParameterValueEnum<?>) objectValue).matchesDBValue(boParameter.getValue());
}else{
isValueMatching = objectValue.equals(boParameter.getValue());
}
result &= isValueMatching;
}
return !result;
} |
Sorry not responding earlier, I had the fix locally all the time.
I have a patch, it is trivial. |
This was referenced Sep 29, 2020
Closed
iloveeclipse
added a commit
that referenced
this issue
Sep 29, 2020
This fixes issue #893 Signed-off-by: Andrey Loskutov <loskutov@gmx.de>
iloveeclipse
added a commit
that referenced
this issue
Sep 30, 2020
This fixes issue #893 Signed-off-by: Andrey Loskutov <loskutov@gmx.de>
iloveeclipse
added a commit
that referenced
this issue
Sep 30, 2020
This fixes issue #893 Signed-off-by: Andrey Loskutov <loskutov@gmx.de>
iloveeclipse
added a commit
that referenced
this issue
Sep 30, 2020
This fixes issue #893 Signed-off-by: Andrey Loskutov <loskutov@gmx.de>
iloveeclipse
added a commit
that referenced
this issue
Oct 6, 2020
This fixes issue #893 Signed-off-by: Andrey Loskutov <loskutov@gmx.de>
Fixed via #1317 |
This was referenced Mar 8, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was hoping 3.1.12 was going to fix this analysis error but I just updated and it is still there. I've had this ever since switching from FindBugs to Spotbugs. My build run under Java 11. Here is one of the errors I get in my log (I get many like it):
The method it is referencing is:
The log is filled with this but it doesn't affect the build. Spotbugs is not reporting an error just logging a failure.
I looked to see if this was reported but didn't find any mention. Is there a way to turn off these messages?
The text was updated successfully, but these errors were encountered: