-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Original issue
As described in 2i2c-org/infrastructure#2108 (comment):
I have a question about quitting an RStudio session. We had a problem with this in our August 2022 event, and the problem is still there. Basically, there's no obvious way to actually quit and stop the server. When one clicks on the "Quit the current R session" button on the upper right, or the equivalent menu item under
File, we get this screen:But that's misleading, because the session doesn't seem to have ended. If we then try to go to the hub login page at https://oceanhackweek.2i2c.cloud, we're taken straight to https://oceanhackweek.2i2c.cloud/user/emiliom/rstudio/
The only solution we found was to go to https://oceanhackweek.2i2c.cloud/hub/home and then click on "Stop my Server". But that's difficult, because event participants need to remember where to find that link!
If on RStudio we click on
Sign outinstead, no real change happens. It's like a refresh, and you're right back in the session.Any advice to address this problem?
I'll add that in our context, where we support both Python and R via different images, the issue of not being able to truly stop the server and quit the session from RStudio has an additional, more immediate impact. If a user wants to quit the RStudio session in order to go back to the login and initiate a Python+JupyterLab session, the only option at this time is the link https://oceanhackweek.2i2c.cloud/hub/home. Otherwise, you're stuck in RStudio!
Background notes
- RStudio isn't the primary server to shut down to stop the JupyterHub started server, that is instead a jupyter
notebookorjupyter_serverserver. - I believe RStudio isn't involved or configured with authentication, so
Sign outdoesn't make sense to present for RStudio in this case I think.
Upstream
- RStudio is started and proxied to using
jupyter-server-proxyviajupyterhub/jupyter-rsession-proxy, where this is already discussed topics.
