-
Notifications
You must be signed in to change notification settings - Fork 148
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
Unstable behaviour of Jupyter-LSP - Losing connection #364
Comments
Hi @qTipTip, thank you for providing the detailed description. There are two issues:
The language servers usually support a debug mode, but we have no way to trigger it from the UI - certainly a thing to think about. I would be curious to know:
|
As to the error code 1006: https://stackoverflow.com/a/19305172/6646912 |
Would you be able to check if it also happens with a different browser (e.g. Chromium or Firefox)? |
Hi @krassowski ! Thank you for looking into this!
Let me know if there is anything else I can provide in terms of info. Here is the packages installed in Docker. FROM jupyter/tensorflow-notebook:04f7f60d34a6 |
Thank you for the update - this helps a lot. I guess that it might be related to another JupyterHub-specific issue, #353. |
Cheers! In which respect is it related to #353? Tell me if I can assist in any way :) |
Same problem, too. @qTipTip , have you solved this problem? I also ran JupyterLab and jupyterlab-lsp in the docker environment similar to you.
@krassowski |
My issue dispappeared with @krassowski/[email protected]! Thanks! |
It seems that this problem is not fully solved after updating to [email protected]. I have exactly the same problem when using jupyterlab-lsp in jupyterhub. The connection was lost after about 30 seconds no typing and didn't reconnect automatically.
|
Same issue, jupyterhub spawing jupyter labs, each user with their own home folder. Happens sporadically for multiple users; can see LSP trying to reconnect after error 1006, but appears to give up after 6 attempts. Refreshing browser reconnects without issue. In some cases, this happens for specific notebooks / files - usually for all. Newly opened files show
|
I believe that the issue behind this is now fixed. In jupyter-lsp 1.1 we enabled pings on websocket to maintain the connection (https://github.com/krassowski/jupyterlab-lsp/pull/459) and in jupyterlab-lsp 3.1 we increased the timeouts for connection to the total of 5 minutes and 30 seconds (https://github.com/krassowski/jupyterlab-lsp/pull/479). I am reluctant to close this without your feedback as I have never experienced this issue, but I would be very keen to understand if the mentioned changes helped you. May I suggest that you try with the latest version (jupyterlab-lsp 3.3.1 and jupyter-lsp 1.1.3 at the moment)? |
Hey @krassowski! That is great news! I am currently working on migrating our JupyterHub deployment to 1.3 with JLab 3.0. Will let you know! |
Hi!
First of all, thanks for an incredibly nice plugin.
I am having some issues with the stability of the plugin, and was hoping you could help me debug it further.
I'll try to describe my issues as detailed as possible.
Current Behaviour
Opening a new notebook
When initially opening a new notebook, with a new kernel, everything seems to initiialize properly. I observe the following messages in the developer console:
At this point in time, the autocomplete seems to be functioning properly, and any modifications to the cell yields
things along these lines:
Losing Connection
Without forewarning, the LSP-plugin loses connection, with the following messages:
Failing to reconnect
Finally, the plugin gets stuck in this loop of the two following states:
Expected behavior
I expect the LSP-plugin to reconnect, and resume working.
Context
Required: installed server extensions
Required: installed lab extensions
Troubleshoot Output
The text was updated successfully, but these errors were encountered: