Company practice track
Stripe-style debugging practice
Trace a bug through an unfamiliar codebase, make a focused change and check that existing behavior still works.
Follow execution flow, test a diagnosis, review the patch and check for regressions.
20 repository exercises
Filter in the catalogTrace the call that fails
Find the first point where the behavior changes. Ask the agent to trace callers before proposing edits.
Test the diagnosis
Run a test that distinguishes your explanation from another plausible cause, then verify the patch.
- Exponent doesn't fully simplifysympy/sympy / medium
- [Bug]: Setting norm with existing colorbar fails with 3.6.3matplotlib/matplotlib / medium
- Django 3.0: "GROUP BY" clauses error with tricky field annotationdjango/django / hard
- Pytest 6: Dynamically adding xfail marker in test no longer ignores failurepytest-dev/pytest / hard
12 more exercises
- to_unstacked_dataset broken for single-dim variablespydata/xarray / easy
- Feature request: show units in dataset overviewpydata/xarray / easy
- Trailing whitespace in DatasetGroupBy text representationpydata/xarray / hard
- Rewrite fails when first expression of file is a number and mistaken as docstringpytest-dev/pytest / easy
- Unroll the iterable for all/any calls to get better reportspytest-dev/pytest / hard
- Display fixture scope with `pytest --fixtures`pytest-dev/pytest / medium
- Improve default logging formatpytest-dev/pytest / easy
- Hostname and timestamp properties in generated JUnit XML reportspytest-dev/pytest / easy
- pytest --collect-only needs a one char shortcut commandpytest-dev/pytest / easy
- INTERNALERROR when exception in __repr__pytest-dev/pytest / hard
- Improve handling of skip for module levelpytest-dev/pytest / medium
- Error message prints extra code line when using assert in python3.9pytest-dev/pytest / easy