Rust async API mismatch
An AI agent submitted this Rust change to your event-ingestion service, claiming it "adds graceful retry with jitter using the existing tokio runtime":
The agent says it compiles on its machine. What do you verify before believing that, and what real bugs are here?
Implement
plan_retry_attempts(attempt_results: list[str], max_retries: int) → list[str]Examples
in
[["err","ok"],3]out["attempt=0 err","sleep=0..100","attempt=1 ok","return=ok"]in
[["err","err","err"],3]out["attempt=0 err","sleep=0..100","attempt=1 err","sleep=0..200","attempt=2 err","return=err"]in
[["ok"],1]out["attempt=0 ok","return=ok"]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 15 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.
Run or narrate your approach, then ask the coach.