Python debugging
310 minInvestigate state, cancellation, request security, and time.
Pick a bug, follow the evidence, and make it click.
A small codebase. A real problem. Your next breakthrough.
A cached result gets computed again. Only some values trigger it.
The combination generator loses the valid zero-choice case.
Redirect filtering works in one client and leaks credentials in another.
ASCII labels render. Localized labels sometimes crash the widget.
A tiny timezone returns the right clock time but marks an ambiguous hour incorrectly.
A request waiter reports success during shutdown when completion and cancellation land in the same event-loop turn.
A reusable HTTP session accepts an untrusted certificate only after an earlier diagnostic request.
A busy worker keeps reacquiring a free permit while older requests starve.
A bounded HTTP client still accepts unbounded interim replies and discarded trailers.
A pattern analyzer panics before it can reject an enormous expression.
A streaming log collector counts one rejected record several times, depending on network packet boundaries.
Start small. Build confidence. Follow a language from easy to hard.
Investigate state, cancellation, request security, and time.
Investigate empty inputs, text, numeric bounds, and streaming parsers.
This is about understanding, not speed.
No leaderboard. No ticking clock. Just you, the evidence, and a bug worth finding.