-
Notifications
You must be signed in to change notification settings - Fork 148
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
Version 4.0.0 breaks SageMaker Studio environment #404
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
As far as I know there's no easy way to investigate this, so I think any fix will have to be contributed by the community. Alternatively if you've got an AWS support contract it might be worth a ticket to find out what's different between the open-source JupyterLab/notebook/server and SageMaker that could lead to this? |
Bug description
Inside of the AWS SageMaker Studio environment, the default version of jupyter-server-proxy is 3.2.1 (3.2.2. also works). Upon running
conda activate studio
andpip install jupyter-server-proxy==4.0.0
, and reloading the browser on path/jupyter/default/lab?
, the home button disappears.Expected behaviour
No change in the UI of SageMaker Studio
Actual behaviour
Studio Home button and Launcher are broken.
How to reproduce
default
(using JupyterLab v3)conda activate studio
pip install jupyter-server-proxy=4.0.0
restart-jupyter-server
Your personal set up
Full environment
Configuration
# jupyterhub_config.py
Logs
The text was updated successfully, but these errors were encountered: