You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #780, the fix for matching maxItems and minItems was changed to check if "oldValue == newValue". But those are both "Integer" and so the equality is doing an object matching, not an equality of the actual integers. It should be "oldValue.equals(newValue)" or "Objects.equals(oldValue, newValue)".
I'm seeing this when the maxItems is a large number. Sometimes, the JVM reuses the same object for the integer and sometimes it doesn't. When it doesn't reuse the same object, then the existing comparison fails.
The text was updated successfully, but these errors were encountered:
In #780, the fix for matching maxItems and minItems was changed to check if "oldValue == newValue". But those are both "Integer" and so the equality is doing an object matching, not an equality of the actual integers. It should be "oldValue.equals(newValue)" or "Objects.equals(oldValue, newValue)".
I'm seeing this when the maxItems is a large number. Sometimes, the JVM reuses the same object for the integer and sometimes it doesn't. When it doesn't reuse the same object, then the existing comparison fails.
The text was updated successfully, but these errors were encountered: