I noticed that the RStudio session is prone to timing out quite rapidly in comparison to the jupyterhub which never appears to timeout before a Renku session itself does. It turns out that RStudio sessions timeout on their own after 2hrs.
(I occasionally have long running sessions where I'm writing something interrupted by meeting etc. where it's convenient to just switch back to my working tab and pick up where I left off. I've been using jupyter hub on a project lately and noticed it coped with this much better than RStudio sessions)
It would be nice if the RStudio timeout was not less than the Renku session timeout by default.
I've been able to address this by adding this line to my Project Docker files:
# Infinite RStudio session timeout
RUN echo "session-timeout-minutes=0" >> /etc/rstudio/rsession.conf
Setting timeout to zero yields an infinite timeout.
Describe the bug
I noticed that the RStudio session is prone to timing out quite rapidly in comparison to the jupyterhub which never appears to timeout before a Renku session itself does. It turns out that RStudio sessions timeout on their own after 2hrs.
(I occasionally have long running sessions where I'm writing something interrupted by meeting etc. where it's convenient to just switch back to my working tab and pick up where I left off. I've been using jupyter hub on a project lately and noticed it coped with this much better than RStudio sessions)
It would be nice if the RStudio timeout was not less than the Renku session timeout by default.
I've been able to address this by adding this line to my Project Docker files:
Setting timeout to zero yields an infinite timeout.
Please see the 'session timeout' section of this page on posit support: https://support.posit.co/hc/en-us/articles/200552316-Configuring-RStudio-Workbench-RStudio-Server for additional details
Link to project Here is a project where I've implemented this fix: https://gitlab.renkulab.io/hdbi/data-management/hdbi-data-outputs-quarto-presentations/-/blob/master/Dockerfile
To Reproduce Steps to reproduce the behavior:
Expected behavior RStudio doesn't timeout before the Renku session does