Async blocking calls: six recorded examples
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
Supply the call, execution context and helper contract. Compare event-loop blocking with explicit worker offload, nonblocking APIs and an ordinary synchronous job.
The important boundary is the executing thread, not the spelling of the function. A synchronous client called inside an async handler still occupies that handler's thread until it returns.
Supply the helper contract and any offload wrapper. Without those facts the same-looking call could be nonblocking, explicitly offloaded or blocking the loop.
This exercise adapts a concrete async-client rule in the linked Jev linter. It reviews a supplied path; it does not profile a running service or measure a response-time improvement.
This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Use the sample to understand the rule, then test your own input for async blocking calls.

Supply the call, execution context and helper contract.

Open the decision rules and keep the intended distinction between Blocks loop, Offloaded or async, Other context, Review. Edit the choices only when testing your own rule.

Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

Review Review before using a result. The label is a decision about the supplied information, not an executed action.
| Original input | Observed label | Leading probability |
|---|---|---|
| Synchronous client in handler | Blocks loop | 99.0% |
| Explicit worker offload | Offloaded or async | 99.0% |
| Nonblocking client | Offloaded or async | 99.0% |
| Synchronous job | Other context | 95.0% |
| Unknown helper | Review | 89.0% |
| Async spelling around a sleep | Blocks loop | 98.0% |
These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json
# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.The input contract and these limits define what the result means.
No. The execution contract still matters. An explicit worker boundary or an appropriate nonblocking implementation changes where or how the work waits.
No. It classifies the supplied code description and context. Use runtime profiling to establish actual timing.
It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.
No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.
Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.