-
Notifications
You must be signed in to change notification settings - Fork 3.7k
fix some LGTM alerts #3531
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
fix some LGTM alerts #3531
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
retest this please |
run java8 test |
1 similar comment
run java8 test |
run java8 tests |
It is not clear to me why that test is failing. ReplicatorTest passed for me locally, and after rebasing against master it still passed. It also doesn't look like something that would be related to the changes I made. |
@1m2c3t4 replicator test is a flaky test. // run java8 tests |
a71c90c
to
f6d17ec
Compare
f6d17ec
to
3251065
Compare
54115d6
to
b5e13f4
Compare
run java8 tests |
Thanks for reviewing and merging @sijie @merlimat @rdhabalia |
Motivation
LGTM has raised some alerts during analysis of apache/pulsar (https://lgtm.com/projects/g/apache/pulsar/alerts/?mode=tree).
Modifications
Array index out of bounds
error in AbstractMetricsHashed value without hashCode definition
in NamespaceServiceReference equality test of boxed types
in PoliciesWrong NaN comparison
in ProducerStatsRecorderImplInconsistent equals and hashCode
where equals had been overridden but hashCode was notVerifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
If
yes
was chosen, please highlight the changesDocumentation