2i2c-org / features

Temporary location for feature requests sent to 2i2c
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Improving secondary RStudio UI: "shut down" and "sign out" #21

Open consideRatio opened 1 year ago

consideRatio commented 1 year ago

Original issue

As described in https://github.com/2i2c-org/infrastructure/issues/2108#issuecomment-1445737407:

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: image 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 out instead, 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

Upstream