Time: 0:00
Test a custom input to verify an edge case (e.g. empty lists, negative numbers, duplicates).
This bug belongs to the logic errors pattern
The wrong operator, an inverted condition, a formula the right way round but backwards.
What went wrong: Java caches boxed wrapper objects only in the range -128 to 127. Values outside this range (like 1000) produce distinct object instances on the heap, so == evaluates to false.
The fix: Compare boxed wrapper objects using .equals(): valA.equals(valB).
Remember: Never use == to compare boxed wrappers (Integer, Long, etc.). Always use .equals().
The pattern behind it: logic errors.
Paste this into any web page or blog post. Visitors fix the bug right there, in their browser.
<iframe src="https://trybughunt.com/embed/224c1137-6247-4b00-ba89-7119802a3604" title="Debugging challenge: Boxed Long equality comparison outside cache range" width="100%" height="580" loading="lazy" style="border:1px solid #d4d4d8;border-radius:12px;max-width:760px"></iframe>
<p style="font-size:14px">Debugging challenge from <a href="https://trybughunt.com/challenges/224c1137-6247-4b00-ba89-7119802a3604">TryBugHunt</a></p>