Open jmcphers opened 1 year ago
There is now support for queuing executions, and examining the queue, in the new kernel supervisor. The work left to do is to hook up the UI so that it submits to this queue, and shows the contents of the queue on reload.
To reproduce, execute a long-running command, then execute a few other commands to queue them up. The queued commands are shown in the Console.
Next, reload the window. The queue is gone; Positron has forgotten what we asked it to run. This is a problem since "queue a bunch of work and close your browser while it goes" is not an uncommon data science workflow.
The current behavior is expected since we store the queue on the front-end; to fix this, we need a way to store (and execute) queued commands even when Positron is not connected to a browser. This probably needs #1155, or something like it, to address.