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 code reads from a closed channel without checking if the channel is still open, leading to unexpected zero values.
The fix: Use the two-value receive pattern to check if the channel is open before reading from it.
Remember: Always use the two-value receive pattern when reading from channels to handle the case where the channel might be closed.
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/d73c65b5-b955-4a4e-98ca-ddda33818778" title="Debugging challenge: Unexpected zero value in concurrent Go program" 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/d73c65b5-b955-4a4e-98ca-ddda33818778">TryBugHunt</a></p>