-
Notifications
You must be signed in to change notification settings - Fork 27
Error on init_datatables_mode() - Comms haven't been initialized properly #30
Comments
Hello! Thanks for the report. This should be fixed now by https://github.com/CermakM/jupyter-require/releases/tag/v0.5.0. Please check. |
I have the same issue :c I have installed |
Could I ask any of you to try this out with python 3.6 if the issue persists please? |
I still get the same issue on py3.7 too; no py3.6 envt to hand to try that right now... |
Please, provide browser console logs and |
hello |
@digitalfox Yes, correct. Thanks for the confirmation. This notebook extension is not compatible with JupyterLab, I am sorry for the inconvenience. @psychemedia EDIT: There is already an existing issue #7 to add JupyterLab support. |
My issue was in notebooks... By the by, I note that in your README, the Binder button points to nbviewer, not a MyBinder link (I was just going to give the demo notebooks a quick test in Binder...) |
Yeah! I have been using jupyter lab. |
@psychemedia Good point, thank you, I'll update the binder link! I think there might be an issue with re-opening notebooks with saved outputs. Either that or Python 3.7 I suppose 😞 |
The link to myBinder is fixed in: 59b4880 |
Hi Marek, thank you the beautiful tool. I am also running into this issue, but only sometimes and only with some notebooks which is particularly puzzling. I have a very large notebook (A) and a freshly created one (B). If I open B and run the init
then it will provide me the comm error, which refreshing the page fixes. For the large notebook A, refreshing the page (which takes up to 15-30s), does not fix the issue and I encounter the comm error. Notebook A was also created before I installed Versions
|
@jvivian-atreca This is a super puzzling error and it's an annoying one. Feel free to investigate, I'd be really glad if somebody helped me with this one as I've been quite short on time lately. Cheers, |
I, also, got the same issue on Centos 8, python 3.6. Workaround for this step was:
before |
Trying an install from pip and direct from the repo, I get an error trying to iniitialise the package as per the docs:
The text was updated successfully, but these errors were encountered: