-
Notifications
You must be signed in to change notification settings - Fork 12
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
Allow to use more recent kernel on interactive_tool_jupyter_notebook #244
Comments
Timothée (first try of computer writing of my little one ;) ) |
The Docker image would need an update: https://github.com/bgruening/docker-jupyter-notebook I guess bumping all requirements or just triggering a new build should do the trick. |
Hello @yvanlebras and @bgruening ! It seems that the Docker image was updated with the new version of the tool (1.0.1) — thank you, @bgruening ! However, I've encountered an issue with this new version. It appears the error is related to the kernel: [TrustNotebookApp] Writing notebook-signing key to /home/jovyan/.local/share/jupyter/notebook_secret This error occurs only when the "Execute notebook and return a new one." option is set to "Yes." Let me know if you have any ideas on how to fix this problem. |
up @bgruening any idea why there is this error on "ir" kernel now you updated the image? Seems to me maybe this is "just" a typo as for me, ir is maybe not the good name of kernel, maybe it is r ? |
Where do you see this? |
Thank you Björn for coming back to us! Here is the stderr of this history https://ecology.usegalaxy.eu/u/ylebras/h/tuto-ecoregionalization step 59:
And @PaulineSGN sent an error from inside eu also if I am not wrong... |
Is that on old notebook created with another Jupyter Notebook instance? Or was this notebook that you try to load generated with the same version? |
oh, you're right... I think it is an old notebook... Will try to update the notebook and come back to you if needed! |
Describe the bug
Not really a bug BUT using interactive_tool_jupyter_notebook tool, we see that R kernel (and others I guess) are using old version:
It is thus difficult or impossible to install recent packages
Galaxy Version and/or server at which you observed the bug
usegalaxy.eu
Expected behavior
it seems to me important to update regularly this tool and thus related docker image so 1/ we can use recent packages/libraries 2/ we allow, using previous versions of the tool, to still use jupitool on worklows using nobooks as input datasets
Additional context
need to take care to keep possibilities to use old versions for jupytool use in workflows
The text was updated successfully, but these errors were encountered: