-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Installing plugin results in jupyterlab version change after restart #15277
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
I did see the warnings on the "Extensions" page but I (wrongly) assumed that it would just mean the plugin woudln't work. |
I think that it would make sense to force-pin the version of jupyterlab in the default (pip) plugin manager implementation, so that it is never changed. That would involve updating: jupyterlab/jupyterlab/extensions/pypi.py Lines 280 to 293 in 9d360bb
In addition we should have |
Thanx, I'm glad it made sense :-) |
Hi @krassowski, I am eager to make my first open source contribution. Could you assign this issue to me and provide some guidance on how I can resolve the issue? |
Thanks for proposing your help @Sarthug99 (as soon as you have commented on an issue you can self assign to it 😉 - we don't have a policy of assigning people to issue). To provide you with some guidance, a way to solve this would be to add a constrain when executing the jupyterlab/jupyterlab/extensions/pypi.py Lines 280 to 293 in 9d360bb
What I would suggest to do is:
with tempfile.NamedTemporaryFile() as fconstraint:
cmd_line = [
with tempfile.NamedTemporaryFile() as fconstraint:
fconstraint.write(f"jupyterlab=={__version__}")
cmd_line = [ You can import
with tempfile.NamedTemporaryFile() as fconstraint:
fconstraint.write(f"jupyterlab=={__version__}")
cmd_line = [
# ...
"--constraint",
fconstraint.name
] |
Damn, got caught out again - blimmin arcgis downgraded me to 3.6. |
I would like to assist in solving this issue |
Hi pipilacha! I'm already working on this issue and am almost done with the implementation... |
I'm not sure what category this falls under - it was certainly unexpected.
We're running the latest 4.0.7 and have plugins enabled for users. A user searched for the "jupyterlab-snippets" plugin and installed it - we'd used it on older 3.x releases. After restarting jupyterlab it appeared we'd downgraded to v3.6. This was totally unexpected!!
Now I guess I have to block this plugin, but I'm not sure why an incompatable plugin was displayed in the search results? Is restricting plugins to just "@jupyterlab/*" going to solve this or am I going to have to disable all plugins so a user doesn't accidently downgrade jupyterlab?
Ideally the search would only bring back plugins that are compatable with the currently installed jupyterlab version, or is there a way of configuring this already that I've overlooked?
thanx :-)
The text was updated successfully, but these errors were encountered: