Github user kjduling commented on the issue:

    https://github.com/apache/incubator-geode/pull/230
  
    No existing test exposed this.  This is in reaction to a code analysis.  
Case by case, the code may or may not be doing what the developer intended 
because of the nature of == vs .equals().  If the == test is true, then the 
.equals() test must also be true.  However, just because == is false does not 
mean .equals() is not true.
    
    Existing testing did not reveal this.  I'll work with Grace to come up with 
tests to verify.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to