What Happens to Work After a Timeout?
Comments on “What Happens to Work After a Timeout?”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
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.
Why it ranked
No. 4 of 122 with a score of 0.74. The panel rated it highest on new information (0.91) and practical relevance (0.88), lowest on significance (0.57). Placed No. 4, No. 6 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Clear, practical explanation of timeouts not stopping underlying work across JS, Python, Go, Rust, with reproducible experiments and idempotency guidance; modest significance, well substantiated by demos, though not a news item and long-winded in places.
- AI judgeJudge 3gpt-5.6-luna
- A technically detailed, cross-language explanation of timeout, cancellation, resource, and idempotency boundaries, supported by runnable examples and practical testing guidance. It is broadly actionable, though the underlying concepts are established rather than landmark.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.74total under rubric v2.3
- Significance0.57
- Reader interest0.78
- Audience breadth0.76
- Practical relevance0.88
- Substantiated0.78
- Technical depth0.87
- New information0.91
- Counts against: Promotional0.03
- Counts against: Overclaim0.11
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.67 | 0.35 | 0.70 | 0.57 | 0.35 | +0.24 | +0.138 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.77 | 0.70 | 0.88 | 0.78 | 0.18 | +0.26 | +0.204 |
| Audience breadthHow many people who build technology does it concern? | 0.87 | 0.60 | 0.82 | 0.76 | 0.27 | +0.13 | +0.099 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.94 | 0.80 | 0.90 | 0.88 | 0.14 | +0.22 | +0.194 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.89 | 0.60 | 0.84 | 0.78 | 0.29 | +0.05 | +0.039 |
| Technical depthHow technically substantive is it? | 0.99 | 0.75 | 0.86 | 0.87 | 0.24 | +0.05 | +0.043 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.85 | 0.90 | 0.98 | 0.91 | 0.13 | +0.05 | +0.046 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.03 | 0.05 | 0.01 | 0.03 | 0.04 | −0.19 | −0.006 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.10 | 0.15 | 0.08 | 0.11 | 0.07 | −0.11 | −0.012 |
| Sum of contributions | +0.744 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.744 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-17/4/"><img src="https://rubric.hrih.si/badge/2026-11-17/4.svg" alt="Ranked #4 on Rubric, 17 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 5 matches source · 3 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenNumber
In the authors' experiment, Node.js 22.16.0 reported the caller timeout at 100ms and the work completed at 350ms.
The article gives no link or citation for it.
The article says “Node.js 22.16.0 100ms Caller timed out 350ms Work completed”
The source says No source to compare with.
No source givenNumber
In the authors' Python 3.13.5 run, the caller timed out at 101ms and the thread completed its work at 351ms.
The article gives no link or citation for it.
The article says “In our run, the caller timed out at 101 milliseconds and the thread printed its completion message at 351 milliseconds”
The source says No source to compare with.
Matches sourceCausal conclusion
Settling Promise.race() does not cancel the losing promises, per the contract of Promise.race().
The cited source says the same thing.
The article says “Settling the race does not instruct the losing promises to stop, and the timer scheduled by work remains in the event loop”
The source says “Settling the returned promise does not cancel the losing operations or unsubscribe the handlers attached to their promises”
Source cited by the article: developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/race
Matches sourceGeneralization
Python's asyncio.wait_for() requests cancellation on deadline expiry, and a suspended coroutine can receive CancelledError and run cleanup code.
The cited source says the same thing.
The article says “asyncio.wait_for() requests cancellation when the deadline expires. A coroutine suspended at an await point can receive asyncio.CancelledError and run cleanup code before terminating”
The source says “If a timeout occurs, it cancels aw and raises TimeoutError”
Source cited by the article: docs.python.org/3/library/asyncio-task.html
Matches sourceQuote
Tokio documents that spawn_blocking() tasks cannot be forcibly aborted after they start.
The cited source says the same thing.
The article says “Tokio documents that spawn_blocking() tasks cannot be forcibly aborted after they start”
The source says “spawn_blocking tasks cannot be aborted once they start running, which means that runtime shutdown will wait indefinitely for all started spawn_blocking to finish running”
Source cited by the article: docs.rs/tokio/latest/tokio/task/fn.spawn_blocking.html
Matches sourceCausal conclusion
When a Tokio timeout expires, the wrapped future is dropped and the remaining instructions in work() are not executed.
The cited source says the same thing.
The article says “When the timeout expires, the wrapped future is dropped. The remaining instructions in work() are not executed, so the completion message does not appear”
The source says “Otherwise, an error is returned and the future is canceled”
Source cited by the article: docs.rs/tokio/latest/tokio/time/fn.timeout.html
No source givenNumber
At 100 requests per second with 30-second operations that continue after timeout, about 3,000 operations are active at steady state, versus about 100 if stopped after one second.
The article gives no link or citation for it.
The article says “100 operations/second × 30 seconds = 3,000 active operations”
The source says No source to compare with.
Matches sourceGeneralization
Go's context Done() channel closes when the context is cancelled, but a function that accepts a context but never reads it is not cancellable.
The cited source says the same thing.
The article says “A context can carry a deadline down a call chain, and its Done() channel closes when that context is cancelled”
The source says “The returned context's Done channel is closed when the returned cancel function is called or when the parent context's Done channel is closed, whichever happens first”
Source cited by the article: pkg.go.dev/context
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 1 pts, not on front page
Recorded for context only, checked 17 Nov 2026, 05:47 UTC. It played no part in the ranking.