Michał Krassowski

Results 1526 comments of Michał Krassowski

Possibly related to: #3400, #2295 and #823.

A less popular [drvic10k/bootstrap-sortable](https://github.com/drvic10k/bootstrap-sortable) manages to handles this case in a clever way, using as many duplicates of rowspan cells as needed to keep a table properly formatted: https://jsfiddle.net/jz5tnq4y/15/. ![peek...

When user executes a long-running cell twice it could be: ```python { "pending_requests": [ { # msg_id of an `shell.execute_request` (allowing to identify subsequent "iopub.status" by parent_header "id": "3ec6186d-dbd2-486e-9622-e771b4bdcc21", "type":...

This is not about concurrent executions but queuing. We need to record the queue to resolve the status properly.

To illustrate if I have a cell: ```python from time import sleep sleep(60) ``` I execute it first time, the `pending_requests` would change to ```python [ { "id": "3ec6186d-dbd2-486e-9622-e771b4bdcc21", "type":...

> In https://github.com/jupyter-server/jupyter_ydoc/pull/197 there is an execution_state field which is equivalent to the status, why isn't that enough? Good question. There are at least two use cases which cannot be...

> For input requests, my vision is that they should be collaborative anyway, maybe using [ypywidgets](https://github.com/davidbrochart/ypywidgets). That way, every client will see the input box with live changes from other...

As a counter proposal, https://github.com/jupyter-server/jupyter_ydoc/pull/227 adds `pending_requests`. We already discussed this at length with @davidbrochart but I am still on fence here. I wanted to highlight it here in case...

To recap, we have three proposals: - a) store `pending_requests` in jupyter-server and expose a dedicated REST API to sync it with frontend https://github.com/jupyter-server/jupyter_server/issues/990 - b) store `pending_requests` in the...

> > You clearly define two different states, but foresee only one indicator for the user. > > My point is that there are not two different states, only one...