-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Jupyter Lab extensions fail to build #2223
Comments
Hmm I think I might have an idea... can you please share the output of Also, please note that you don’t need to use NPM yourself directly to install anything: Jupyter Lab uses NPM under the hood so that’s why the error comes from there but there’s nothing you should need to do yourself with it :) |
I have the same issue. Here is the output of
|
Ok, and does the build succeed with versions 1.5.0 of the Plotly extensions? |
Hello, I am having the same error for a week. For now I am using orca to generate the graphs. Same problem occurs with v1.5.0 of plotly extensions. |
I'm having the exact same issue with a clean conda env and pip installs under Ubuntu 18.04LTS with python 3.6.7, jupyterlab 1.2.0, ipywidgets 7.5.1, plotly 4.5.1, plotly-express 0.4.1, nodejs 13.9.0. |
it would really help if everyone chiming in here could include the output of |
Here is the Dockerfile I am using :
Those are warnings and error that happens during build
Here is the output of
Here is the output from my last working setup of
I modified my docker to use v1.3 of plotly extensions, but it throws the same error, and same result for Hopes it help |
Extremely helpful, thank you @matdecac ! This error doesn’t have the same cause as the one I have previously encountered, so I will have to investigate more fully next week. If anyone else encounters an installation problem, please continue to provide similar details so I can determine if we have one or many issues to tackle :) |
@nicolaskruchten here comes the
|
Here is the output of
|
Same issue here.
where my logfile says:
edit: related: yet to find a workaround though |
Hi, I have the same issue. It appeared suddenly. Two days ago, build was successful. Today, I created a new conda env (copy from a environment.yml with the exact same packages) and it fails.
and the log file
|
Ok so we released versions 1.5.1 of the extensions this past Wednesday... maybe something in there causes this but some people are reporting the same issue with the weeks-old 1.5.0 versions of the extensions. If anyone has a chance to try with a clean environment and the 1.5.0 extensions I’d love to know if this still happens. I’ve not been able to reproduce this issue myself yet. |
Tested extensions with explicit 1.5.0 version under fresh win10 env but got same error :-(. jupyter labextension list:
Error log:
|
folks, I think you could change reference in the CI build (or whenever you're specifying NPM related content) to reference |
is there any workaround? |
I'm also running into the same issue. jupyterlab-plotly v1.2.0 Output:
/tmp/jupyterlab-debug-aeoez37q.log: |
Same problem with me!
|
OK I think I have enough info to fix this, I should have a fix in a day or two, thanks for the information everyone! |
The root cause of this problem appears to be a bad version of https://www.npmjs.com/package/@types/plotly.js which is something we depend on but do not maintain. In principle I could just pin the version to a known-working one here: https://github.com/plotly/plotly.py/blob/master/packages/javascript/jupyterlab-plotly/package.json#L35 and release versions 1.5.2 of our extensions. I will try to do this tonight (Pacific Time). |
@nicolaskruchten |
@peterblazejewicz yes, thanks, your comment above pointed the way. I rather wish that the |
OK I've pushed up versions 1.5.2 of the extensions, so that should resolve the current issue! |
Thanks for your quick work on this. I followed the instructions here again, changing all |
I had exactly the same issue since yesterday, I followed the same instructions as @dr-kinder said, and at last it works after more than twelve hours of investigation. The Plotly v1.5.2 fixes that issue. Thanks to everybody. |
Thank for your prompt intervention. However, now that the buld finishes cleanly, the extension is still not working. I am seeing only a blank container where the plot should be. If I use a widget, I only see a I installed the exact versions (for python and JS versions of plotly) as stated in the update README. Can this be the cause of my problem? The browser console contains the following output:
|
@andrei91ro that sounds like a different issue... could you please create a new one so that others can find it and contribute? |
(base) C:\Users\10055>jupyter lab build (base) C:\Users\10055>jupyter labextension list Build recommended, please run (base) C:\Users\10055> |
@GIShkl can you please open a new issue for this and include the contents of the log file? |
(in general, let's please not add on to old, closed issues like this and instead open up new ones :) |
I am attempting to install Plotly extensions to the Jupyter Lab environment as described in the "JupyterLab Support (Python 3.5+)" instructions here.
Whenever I attempt a build, or a
jupyterlab extension install ...
without the--nobuild
option, installation fails. The trouble comes fromnpm
, but I cannot find any information about this error.For more information on the problem, this is the result of an attempted build:
These are the contents of the log file:
I successfully installed plotly and d3 with
npm
.I am running Python 3.7.6, Jupyter Lab 1.2.6, IPyWidgets 7.5.1, Yarn 1.22.0, and Node 13.8.0.
All Python packages were installed using
pip
.The text was updated successfully, but these errors were encountered: