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

[DISC]: users upgrading jupyterlab in a bucket #91

Open
asreimer opened this issue Jul 13, 2021 · 1 comment
Open

[DISC]: users upgrading jupyterlab in a bucket #91

asreimer opened this issue Jul 13, 2021 · 1 comment
Assignees
Labels
discussion Let's talk about this before doing anything

Comments

@asreimer
Copy link
Contributor

Upgrading jupyterlab within a bucket causes unexpected behaviour. @pmreyes2 reports:

I tried resen-core 2020.2.0 and installed there jupyterlab==3.0.16 . This might be breaking some other things on resen-core 2020.2.0 because the not stopping is not the only issue, it also breaks the jupyter lab itself, resen can't stop it and the browser shows a blank page too. Though it is still alive because http://localhost:9000/tree works but not http://localhost:9000/lab

This is something that we can reasonably expect a user to do and the proof is that a user has done this. So how do we proceed?

  1. Strongly worded warning for the users in the documentation to not do this?
  2. Provide a way to upgrade jupyterlab without breaking things?
@asreimer asreimer added the discussion Let's talk about this before doing anything label Jul 13, 2021
@asreimer asreimer changed the title [DISC]: [DISC]: users upgrading jupyterlab in a bucket Jul 13, 2021
@pmreyes2
Copy link
Contributor

pmreyes2 commented Jul 13, 2021

For your item 2. I just tested a way to upgrade without breaking things:

  • After upgrading jupyterlab you should shutdown JupyterLab from the Menu -> File -> Shutdown.
  • Then within resen you should stop the bucket because resen has no way (yet) to know that the bucket has been shutdown using the browser.
  • From now on the start/stop bucket works.
  • This has been tested with resen-core version 2020.2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Let's talk about this before doing anything
Projects
None yet
Development

No branches or pull requests

3 participants