kiteco / issue-tracker

User-reported issues for Kite
https://Kite.com
1.75k stars 136 forks source link

Kite not working on Jupyter Lab on Debian 10 and prevents kernel from launching #340

Open anoetzli opened 4 years ago

anoetzli commented 4 years ago

I run jupyter lab on a server running Debian 10 and access it remotely. I installed Kite using the following commands:

pip install jupyter-kite jupyter labextension install "@kiteco/jupyterlab-kite"

After installation I realised the labextensions were not enabled, so I enabled them.

I stopped and started jupyter lab (nohup jupyter lab &). I got a message saying that Kite was not installed, and after some time it said Kite was disconnected and asked me to reload the page. Reloading the page made no difference to the Kite disconnected message.

image

image

While Kite was enabled I was unable to run any cells until some minutes after launching jupyter lab. When I disabled Kite, I was able to run my cells again.

No amount of restarting Jupyter Lab (jupyter notebook stop 8888/nohup jupyter lab &) fixed any of these issues.

I then tried to uninstall Kite and reinstall it.

After starting JL, the kernel was in an initializing state for a very long time, and I wasn't able to run any cells until Python was idle (this took many minutes).

image

image

Since uninstalling and reinstalling Kite, the Kite status doesn't appear on the bottom left and the labextension list has an entry in Uninstalled core extensions:

jupyter labextension list:

jupyter labextension list JupyterLab v2.1.5 Known labextensions: app dir: /home/terra15/miniconda/envs/watercorp/share/jupyter/lab @kiteco/jupyterlab-kite v1.0.0 enabled OK @lckr/jupyterlab_variableinspector v0.5.1 disabled OK

Uninstalled core extensions: @kiteco/jupyterlab-kite

pip list:

Package Version


appdirs 1.4.4
attrs 19.3.0
backcall 0.2.0
bleach 3.1.5
certifi 2020.4.5.1
chardet 3.0.4
cycler 0.10.0
decorator 4.4.2
defusedxml 0.6.0
entrypoints 0.3
funcsigs 1.0.2
h5py 2.10.0
idna 2.9
imageio 2.8.0
importlib-metadata 1.6.1
importlib-resources 3.0.0
ipykernel 5.3.0
ipython 7.15.0
ipython-genutils 0.2.0
jedi 0.17.1
Jinja2 2.11.2
json5 0.9.5
jsonschema 3.2.0
jupyter-client 6.1.3
jupyter-core 4.6.3
jupyter-kite 1.0.0
jupyterlab 2.1.5
jupyterlab-server 1.1.5
kiwisolver 1.2.0
Mako 1.1.3
MarkupSafe 1.1.1
matplotlib 3.2.2
mistune 0.8.4
mkl-fft 1.0.15
mkl-random 1.1.1
mkl-service 2.3.0
nbconvert 5.6.1
nbformat 5.0.7
networkx 2.4
notebook 6.0.3
numpy 1.18.5
packaging 20.4
pandas 1.0.5
pandocfilters 1.4.2
parso 0.7.0
PeakUtils 1.3.3
pexpect 4.8.0
pickleshare 0.7.5
Pillow 7.1.2
pip 20.0.2
prometheus-client 0.8.0
prompt-toolkit 3.0.5
ptyprocess 0.6.0
pycryptodome 3.9.8
pycuda 2019.1.2
Pygments 2.6.1
pyparsing 2.4.7
pyrsistent 0.16.0
pyserial 3.4
python-dateutil 2.8.1
pytools 2020.2
pytz 2020.1
PyWavelets 1.1.1
pyzmq 19.0.1
reikna 0.7.5
requests 2.24.0
scikit-image 0.17.2
scipy 1.4.1
Send2Trash 1.5.0
setuptools 47.1.1.post20200604 six 1.15.0
SQLAlchemy 1.3.17
terminado 0.8.3
testpath 0.4.4
tifffile 2020.6.3
tornado 6.0.4
tqdm 4.46.1
traitlets 4.3.3
urllib3 1.25.9
wcwidth 0.2.4
webencodings 0.5.1
wheel 0.34.2
zipp 3.1.0

anoetzli commented 4 years ago

Marking as invalid - Closing issue because I just realised I need a newer version of Jupyter Lab

anoetzli commented 4 years ago

Actually, after upgrading to Jupyter lab v2.2.4 Kite is still coming up as "not installed/disconnected", so reopening this one.

There is another known issue I encountered whereby the Kite was in both the installed and uninstalled extension list, which prevented it from showing at all in Jupyter lab. You can fix this issue by following the suggestion in here: https://discourse.jupyter.org/t/extension-shows-up-as-both-installed-and-uninstalled-and-doesnt-work/2688/3

After removing the offending file ("build_config.json"), I got the following (correct) extension list. jupyter labextension list JupyterLab v2.2.4 Known labextensions: app dir: /home/terra15/miniconda/envs/watercorp/share/jupyter/lab @kiteco/jupyterlab-kite v1.0.0 enabled OK @lckr/jupyterlab_variableinspector v0.5.1 disabled OK

itsdhung commented 4 years ago

Do you happen to have multiple kernels installed or are you using a containerized/remote instance of JupyterLab?