Queued messages, cancels and deliveries now go through one queue object instead of scattered globals.
What's wrong with this entry?
The print and stream-JSON input loops no longer call scattered queue helpers or read module-level globals; queued user messages, cancels and wake-router deliveries all go through one queue object with named methods, and the query builder is handed that object rather than reaching for a global. No behaviour change.
- Methods include enqueue, remove, peek, subscribe, dequeueAllMatching, markCancelPending, isFoldInFlight, recheckCommandQueue, hasUserIntentCommandsInQueue and getCommandQueueLength.
- The
queue_depthtelemetry field and thequeue_depth_at_exitfield ofcli_drain_queue_completenow read from that object.
cli_drain_queue_complete, queue_depth
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.232
Command queue is a single adoptable instance
Both mention queue