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
Raise ceiling on jupyter_server dependency to < 3 #13068
Conversation
Thanks for making a pull request to jupyterlab! |
@fcollonval, woah sorry I checked in the setup.cfg! Apparently I was using an old copy of jupyterlab 😆 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Zsailer for both PRs
woah sorry I checked in the setup.cfg! Apparently I was using an old copy of jupyterlab laughing
Don't worry about it
We also needed to relax the dependency in notebook_shim: jupyter/notebook_shim#12 I'll cut a release in the next hour or so. |
Benchmark reportThe execution time (in milliseconds) are grouped by test file, test type and browser. The mean relative comparison is computed with 95% confidence. Results table
Changes are computed with expected as reference.
Waiting for localhost:8888 Cell memory leaksCreate a code cellMemory change: -243 kB Leak detected: NoLeaking objects:
Leaking collections:
Create a markdown cellMemory change: -195 kB Leak detected: NoLeaking objects:
Leaking collections:
Create a raw cellMemory change: -152 kB Leak detected: NoLeaking objects:
Leaking collections:
Move a code cellMemory change: -408 kB Leak detected: NoLeaking objects:
Leaking collections: Move a markdown cellMemory change: -409 kB Leak detected: NoLeaking objects:
Leaking collections: Move a raw cellMemory change: -349 kB Leak detected: NoLeaking objects:
Leaking collections: File editor memory leaksCreate a fileMemory change: -101 kB Leak detected: NoLeaking objects:
Leaking collections:
Notebook memory leaksCreate a notebookMemory change: -12.7 kB Leak detected: NoLeaking objects:
Leaking collections:
4 passing (13m) |
@fcollonval Do you want to create 3.5.x branch now? I can backport this to PR to that branch. |
@Zsailer thanks for proposing - I would like to wait for the list of PRs to be frozen before doing so (Sept 21st). That leaves us the ability to do patch release on 3.4.x without increasing maintenance load by backporting things twice. |
@meeseeksdev please backport to 3.5.x |
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
And apply the correct labels and milestones. Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon! Remember to remove the If these instructions are inaccurate, feel free to suggest an improvement. |
…#13178) Co-authored-by: Zachary Sailer <zsailer@apple.com>
References
Discuss in today's Jupyter Server meeting.
Also see jupyterlab/jupyterlab_server#302. While it's not strictly necessary to merge+release that PR, first, this PR isn't useful until jupyterlab_server relaxes its pin.
Code changes
This raises the ceiling on JupyterLab's jupyter_server dependency.
This is a temporary change. I think we want JupyterLab 4.0 to depend on Jupyter Server 2.0, i.e.
jupyter_server~=2.0
once Jupyter Server 2.0 reaches final release. JupyterLab 4.0 won't work with Jupyter Server 1.0 (since RTC will likely rely on Jupyter Server 2.0 features).This change should also be backported to a JLab 3.5 branch/release, but we'll keep this change as-is going forward—users can always use either JS 1.x and 2.x in JLab >= 3.5
User-facing changes
This enables folks to test Jupyter Server 2.0 with JupyterLab 4.0.
Backwards-incompatible changes
None.
cc @fcollonval