What Happens to Work After a Timeout?
Comments
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Summary
Emad Khair at octri.dev shows that a timeout limits how long a caller waits, not how long the work runs. In his test, a 350 ms operation behind a 100 ms deadline returned an error on time in Node.js and Python, then finished anyway. Go contexts and Tokio futures cancel only what observes them, and blocking threads keep running. Khair recommends propagating one deadline, bounding concurrency, using idempotency keys for retries, and tracking work that outlives its caller. His capacity figures are idealized arithmetic.