Prep RoomSign inStart free
Code RoomRetry exception handling scope expanded
HardPrep Room Coding #4019

Retry exception handling scope expanded

Vibe & agenticCode quality & reviewSenior–Staff~16 min

An agent refactored this Python retry helper 'for clarity.' The tests pass and the diff looks tidier. You didn't write the original and the change is subtle. What behavior changed, and how would you have caught it without staring at the diff?

The original had caught only `TimeoutError`; the refactor 'tidied' the except to also include `ConnectionError`.

Implement
applied_effect_count(attempt_outcomes: list[str], retry_connection_errors: bool, max_attempts: int) → int
Examples
in[["dropped-after-send","ok"],false,3]out1
in[["dropped-after-send","ok"],true,3]out2
in[["timeout","timeout","ok"],true,5]out1
What a strong answer looks like

Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.

0:00 of about 16 min

Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.

Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.