Skip to content
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

Update to JupyterLab 4.0.0a24 #6371

Merged
merged 9 commits into from
Apr 26, 2022
Merged

Update to JupyterLab 4.0.0a24 #6371

merged 9 commits into from
Apr 26, 2022

Conversation

jtpio
Copy link
Member

@jtpio jtpio commented Apr 25, 2022

Bring in the latest fixes and improvements from https://github.com/jupyterlab/jupyterlab/releases/tag/v4.0.0a24

  • Update to the latest lab 4.0 pre-release
  • Remove deprecated webpack loaders

@jtpio jtpio added this to the 7.0 milestone Apr 25, 2022
@github-actions
Copy link
Contributor

Binder 👈 Launch a Binder on branch jtpio/notebook/update-lab

@jtpio
Copy link
Member Author

jtpio commented Apr 25, 2022

Looks like we are now getting this extra icon by default, even though no preferred path is set:

image

@jtpio
Copy link
Member Author

jtpio commented Apr 25, 2022

Looks like this was added in jupyterlab/jupyterlab#12297.

@jtpio
Copy link
Member Author

jtpio commented Apr 25, 2022

So debugging this, it seems to be because in the case of notebook using a different page config than JupyterLab Server, preferredPath is not set:

image

@jtpio jtpio marked this pull request as ready for review April 26, 2022 06:39
@jtpio jtpio merged commit 18a36d5 into jupyter:main Apr 26, 2022
@jtpio jtpio deleted the update-lab branch April 26, 2022 06:56
@jtpio
Copy link
Member Author

jtpio commented Apr 26, 2022

So debugging this, it seems to be because in the case of notebook using a different page config than JupyterLab Server, preferredPath is not set:

For now we can use the same logic as in JupyterLab Server (ce898be).

We should then consider using the LabHandler directly.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant