Time: 0:00
Test a custom input to verify an edge case (e.g. empty lists, negative numbers, duplicates).
This bug belongs to the async and race conditions pattern
A missing await, unbuffered channel deadlocks, ConcurrentModificationException, and data races under load.
What went wrong: The original code submitted Runnable tasks to the ExecutorService but did not collect their results, leading to lost output.
The fix: Use Callable tasks instead of Runnable, submit them, and call Future.get() to retrieve and print their results.
Remember: Always retrieve results from asynchronous tasks using Future.get() to avoid losing data.
The pattern behind it: async and race conditions.
Paste this into any web page or blog post. Visitors fix the bug right there, in their browser.
<iframe src="https://trybughunt.com/embed/85776294-0330-4f63-8bae-c3507cc48dbe" title="Debugging challenge: Task results lost when ExecutorService tasks complete" 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/85776294-0330-4f63-8bae-c3507cc48dbe">TryBugHunt</a></p>