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

RStudio version is out of date #154

Closed
gavin-k-lee opened this issue May 12, 2021 · 3 comments · Fixed by #157 or #218
Closed

RStudio version is out of date #154

gavin-k-lee opened this issue May 12, 2021 · 3 comments · Fixed by #157 or #218

Comments

@gavin-k-lee
Copy link
Contributor

  • The current RStudio version is pinned at 1.2.5042 but the latest is 1.4.

    ENV RSTUDIO_VERSION 1.2.5042

  • There are a few nice upgrades, for example using renv instead of packrat as the default package manager.

  • The fix would need testing.

@gavin-k-lee
Copy link
Contributor Author

There does not yet seem to be a reliable fix - but it is a (well) known issue now: see
2i2c-org/upstream#12

@TaoSunVoyage
Copy link
Contributor

If you want to use RStudio 1.4.x, you need to set the RSESSION_PROXY_RSTUDIO_1_4 environment variable. This adds additional parameters to the execution of server.

https://github.com/jupyterhub/jupyter-rsession-proxy

@TaoSunVoyage
Copy link
Contributor

TaoSunVoyage commented Aug 18, 2021

I built an image st714/test:bioc with jupyter-rsession-proxy=1.4, RStudio=1.4.1717, R=4.1.0, bioc=3.13

I tested this image in two situations:

  • go to RStudio from JupyterLab
  • go to RStudio by changing the endpoint from /lab to /rstudio

Locally, both worked.

In Renkulab (JupyterHub):

  • Clicking RStudio button in JupyterLab redirected to https://renkulab.io/auth-sign-in?appUri=%2F (404 error)
  • Changing the endpoint from /lab to /rstudio/auth-sign-in?appUrl=%2Fworked, which is a kind of workaround

There is soon going to be a release of jupyter-rsession-proxy to fix the issue with RStudio1.4, see jupyterhub/jupyter-rsession-proxy#97 and jupyterhub/jupyter-rsession-proxy#107.

I built another image st714/test:bioc-fix with this fix jupyterhub/jupyter-rsession-proxy#107 and there seemed to be no critical issue.

Suggest we wait for the new release of jupyter-rsession-proxy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants