Prep RoomSign inStart free
Code RoomVerify an agent upload fix
MediumPrep Room Coding #5007

Verify an agent upload fix

Vibe & agenticAlgorithms & data structuresMid–Senior~18 min

A user reported that uploading a file over 5 MB sometimes fails with a 500. You gave the stack trace to an AI agent and it returned a fix that wraps the upload handler in a try/catch and returns a friendly 413 instead. The error stopped appearing in your manual test. How do you decide whether this fix addresses the root cause or just hides the symptom — before you merge it?

Implement
classify_upload_failure(size_bytes: int, limit_bytes: int, error_kind: str) → str
Examples
in[6000000,5000000,"body_size_exceeded"]out"size_cap:accept_413"
in[5200000,10000000,"body_size_exceeded"]out"misconfigured_limit:reject_fix"
in[5200000,10000000,"out_of_memory"]out"memory_pressure:reject_fix"
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 18 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.