Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Buffered message don't replay but discarding #5243

Closed
NEOherozzz opened this issue Feb 20, 2020 · 8 comments
Closed

Buffered message don't replay but discarding #5243

NEOherozzz opened this issue Feb 20, 2020 · 8 comments

Comments

@NEOherozzz
Copy link

Hi,

Recently, I have some troubles with replaying buffered message. When running some cells, and close chrome tab. A few minutes later, reopen it. The running cells message don't show below the cells.

I have read #4105, #4110. So I run conda install -c conda-forge jupyterlab to update the version of notebook. but the problem still exists.

This is the output of jupyter troubleshoot.
jupyter troubleshoot.log

This is the output of jupyter lab --debug.
jupyter lab --debug.log

In jupyter lab --debug, I just open chrome tab, running cells below. When it running on cell 3, I close it, wait some minutes and reopen it. But the buffered messages don't show.
jupyterlab

Does anybody know how to solve it? Thanks in advance!

@NEOherozzz
Copy link
Author

Does anyone has ideas to fix this?

@amangarg96
Copy link

@NEOherozzz Not a fix, but a work around - do not close/refresh the chrome tab.

Once you refresh the chrome tab, the messages from the kernel do reach the browser but the cell and message mapping is lost, so the browser does not know on which cell to render the output.

To reconnect to the kernel, use the 'Reconnect to kernel' button instead -
image

@lfdversluis
Copy link

lfdversluis commented Feb 17, 2021

Got the same issue. I closed my browser tab because I had a long running process and turned of my pc (jupyter lab is running headless remote). Saw nothing in the morning and only Discarding 200 buffered messages for ... in the console. @amangarg96's suggestion does not work for me as it perfectly fine was still connected to the kernel (now idle). Reconnecting to kernel did nothing for me.

@amangarg96
Copy link

Hi @lfdversluis ,
My suggestion was only for cases when the tab has not been closed or refreshed.

I don't think there's any way to retrieve the messages once the message-to-cell mapping is lost

@dsvanidze
Copy link

Is there any solution? It is important to get all outputs and messages for an active kernel after refreshing a tab or closing a browser window.

@huaiyizhao
Copy link

This feature is badly needed. Imagine when you run the code on a remote server yesterday and no output shows on your reconnected browser tab now

@kevin-bates
Copy link
Member

This is definitely something we'd like to support, but will likely not happen here. We're hoping the recent addition of cell-ids may be useful here - along the lines of @amangarg96's comment above. As a result, I'm going to (attempt to) move this to Jupyter Server...

@meeseeksdev migrate to jupyter-server/jupyter_server

@lumberbot-app
Copy link

lumberbot-app bot commented May 5, 2021

Done as jupyter-server/jupyter_server#508.

@lumberbot-app lumberbot-app bot closed this as completed May 5, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants