You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2017/07/09 01:57:01 UTC

[jira] [Updated] (STORM-2503) lgtm.com alerts: bugs in equality and comparison operations

     [ https://issues.apache.org/jira/browse/STORM-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jungtaek Lim updated STORM-2503:
--------------------------------
    Fix Version/s: 1.2.0
                   1.1.1

> lgtm.com alerts: bugs in equality and comparison operations
> -----------------------------------------------------------
>
>                 Key: STORM-2503
>                 URL: https://issues.apache.org/jira/browse/STORM-2503
>             Project: Apache Storm
>          Issue Type: Bug
>            Reporter: Aditya Sharad
>            Assignee: Aditya Sharad
>             Fix For: 2.0.0, 1.1.1, 1.2.0
>
>          Time Spent: 5h 10m
>  Remaining Estimate: 0h
>
> There are a number of alerts found by lgtm.com at https://lgtm.com/projects/g/apache/storm/alerts/ that indicate genuine bugs in comparison operations in the Storm code.
> These rules include:
> * Equals on incomparable types (leading to bugs in comparison or caching)
> * Hashed value without hashCode definition
> * Inconsistent equals and hashCode (together with the previous one, this indicates some missing {{hashCode}} implementations)
> * Comparison of identical values (indicating incorrect comparator logic in {{DefaultResourceAwareStrategy}})
> * Useless comparison test (indicating a variable name typo)
> * Suspicious reference equality test of boxed types (indicating a spurious use of {{==}} instead of {{equals}} on boxed types)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)