JupyterLab extension not getting installed correctly
See original GitHub issueThe JupyterLab extension isn’t getting installed correctly using the provided lifecycle configuration hooks in both Notebook instances and Studio.
Part of the reason seems to be due to the fact that it is referencing an old repo ("https://github.com/awslabs/sagemaker_run_notebook.git
) here which doesn’t exist anymore.
Should it be replaced with the current repo? Is any one using this extension?
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Jupyter lab extensions not working · Issue #8122
I installed jupyter lab extensions, which are enabled, but do not work. They appear in the extension manager, but still then they do...
Read more >What to do when things go wrong - The Jupyter Notebook
Try disabling any browser extensions and/or any Jupyter extensions you have installed. Some internet security software can interfere with Jupyter. If you have ......
Read more >@jupyterlab
When using a version of Jupyter Notebook earlier than 5.3, the following command must be run after installation to enable the JupyterLab server...
Read more >Installing extension at user level
When using the command line, you can target the --level of the config: user , system , or sys-prefix (default). However it is...
Read more >JupyterLab build is suggested and successfully installed ...
Solution: Deactivate firewall and run the following command in a windows command prompt: · The details: This turned out to be a firewall...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I got this working by updating the Git URLs in the code to this repo. I have created a PR with the required changes.
I also have a few releases in my personal fork with these changes which are working for me. Feel free to use that or build your own release and use that until the issue in this repo is fixed.
Happy to help with any questions that anyone might have.
I don’t think that those URL changes would fix these problems. While you are correct that those are the wrong URLs, I believe they are only used to document the package, not as part of the installation.