Bug Hunt
The Enum Case Nobody Handled and the Compiler Did Not Catch
A new status was added to the model and the match statement had no default, so the new value fell through to the fallback branch, and the order was silently…
Long form accounts of single debugging investigations, false leads included. The wrong turns are the part you learn from.
Bug Hunt
A new status was added to the model and the match statement had no default, so the new value fell through to the fallback branch, and the order was silently…
Bug Hunt
The collation differed between the containers, so the same query returned the rows in a different order, and the pagination showed duplicates and gaps…
Bug Hunt
The cleanup removed expired entries while iterating the mapping, and the interpreter raised the size-changed error, and on the runs that did not raise it…
Bug Hunt
The field was parsed as a number on import, so the codes starting with zero lost a digit, and the shipping lookup failed for a whole region, and the failure…
Bug Hunt
The helper sorted the array in place and returned it, so the caller's original was reordered too, and the second consumer saw a list nobody had touched, and…
Bug Hunt
The identifier came back from the API as a number, and the number exceeded the safe integer range, so the parsed value rounded, and the lookup found a…
Bug Hunt
The sort threw an inconsistent comparison error on one dataset, because the comparator said a beat b and b beat c but c beat a, and the sort trusted the…
Bug Hunt
The pattern matched as much as it could instead of as little as it needed, so one capture group ate the delimiter and the two fields after it, and the parse…
Bug Hunt
The checkout request timed out but the server had already applied the discount, so the retry applied it again, and the order total went below the coupon's…
Bug Hunt
A newer embedding model went live for queries while the index still held the old vectors, and the two spaces were unrelated, so similarity became noise and…
Bug Hunt
The generated pattern passed every test in the suite, then a single long string made it run for nine minutes. The pattern was not wrong.
Bug Hunt
The report listed tomorrow's events before today's, and the comparison never raised an error, only returned the wrong order, because aware and naive…