The REPL tool could return a receipt and deliver results later, but that path is compiled off.
Async REPL dispatch with background poll delivery is behind a build-time constant that is false here.
What's wrong with this entry?
The REPL tool can now hand a script to a dispatcher, return a receipt immediately and deliver the real result later as a background poll event. The gate is a build-time constant that is false here, so every call runs the synchronous path.
- The tool's output schema gained an
asyncDispatchedboolean. - There is a cap on how many dispatches can be outstanding; past it, further dispatches are refused.
- Both the receipt and the refusal text point at a
<event kind="repl-eval">poll event, with the receipt assembled at runtime around the evaluation id and current queue depth. - Settle handling runs a PostToolUse pass over the deferred result, so hooks still see it.
asyncDispatched
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
Query handling moved out of the REPL component
Both mention repl
-
v2.1.236
REPL streaming state moved into a single object
Both mention repl
-
v2.1.236
Turn and streaming handling moved onto one controller
Both mention repl