-
Notifications
You must be signed in to change notification settings - Fork 56
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
conf_jupyter.sh fails #22
Comments
Hi @Kevin--R Kevin--R, Unfortunately you are right - I was able to reproduce your findings but I have no new workaround as of yet. I only can get
Hope this helps for the moment - I'll try to find a way to automate it (again). If this works for you or if you or anybody else finds a fix, please do let men know. - Thanks |
Hi @Kevin--R,
|
@Kevin--R: you were faster to identify jupyter-widgets/ipywidgets#2061 -- I just downgraded nodejs using |
Hi @kleinee First off I wanted to thank you for the time and effort you put into creating this great resource. I have one jupyter lab server set up and running and I'm currently trying to set another one up for a friend. I've tried a clean install starting with a freshly imaged SD card and ./conf_jupyter.sh still fails.
I used the manual workaround you described above with the following results:
It runs to this point then it gets stuck in a loop. I got to this point several days ago and let it run overnight and it was still at this point the next morning. It seems there is some issue caused by node updating to version 10 causing failures with jupyter-widgets-jupyterlab-manager installing. I can usually puzzle my way through issues with linux or python as I have some experience with them (but I'm far from being an expert). I've tried to follow the issue with jupyterlab-manager here on GitHub but I'm kind of at a loss as I know absolutely nothing about node / yarn.
|
wow you're quick I ran |
@Kevin--R please see my comment above. I did not notice this before you reported the tragic return of issue 16 because I had no reason to upgrade nodejs. When you opened the issue I ran a fresh install. Happy to report that with |
looks like we're posting at the same time thanks again for creating this great resource |
@Kevin--R Glad you like it. And by the way: I am no nodejs expert either... |
Yesterday evening I did a complete fresh install on a newly imaged SD card and After a few attempts, I noticed that if I just call I found this info. on the page for n-install here: https://github.com/mklement0/n-install Using this method, I just finished a complete fresh install without errors and without making any changes to your scripts. |
bash -i inst_node.sh |
@kleinee I'm getting kind of cross eyed after sitting in front of the computer all morning - sorry for the confusion |
in answer to your question, node v8.11.2 (lts) and v10.1.0 (latest) were installed by your scripts and v8.11.2 was made active |
@kleinee
it appears that if the calling script ( |
You are right - thanks for the feedback! Since we now call |
@kleinee When you call
fail beccause the path to the node executable is not in the environment path. If you change conf_jupyter.sh to:
Then if you call This will also eliminate the need for the script |
Looks like issue #16 may have returned:
The text was updated successfully, but these errors were encountered: