Investigating possible issues with RStudio Version 3.20.0 application configuration
Problem
The Terra team is investigating a potential issue related to the latest version (3.20.0) of the RStudio application configuration.
Users may see issues changing between Jupyter and RStudio environment configurations when choosing to keep their Persistent Disk.
Users may also see problems when trying to open files in RStudio that were created using a previous version of RStudio.
Workaround
If you are unable to successfully change between Jupyter and RStudio, you can get around the issue by:
- Using gcloud storage cp to copy any data you still need out to another location, such as your workspace bucket.
- Deleting the cloud environment and Persistent Disk. This is permanent, so please make sure you have the data you need saved elsewhere before you delete the Persistent Disk!
- Creating a new cloud environment and Persistent Disk.
- Copying any relevant data to the new Persistent Disk.
These steps may also allow you to open files generated in an older version of RStudio.
We will update this Known Issue with new information as the investigation progresses.
Comments
1 comment
UPDATE
We have rolled back the RStudio version. At this time, users are once again able to swap between Jupyter and RStudio cloud environments using the same disk. Users should also be able to use files generated from older versions of RStudio.
If you are still experiencing the issue, please recreate your RStudio environment by following these instructions:
1) Open the Application Configuration panel and select "Edit existing Environment"
2) Select the configuration with Bioconductor 3.19
3) Click Update at the bottom
You can alternatively create a fresh environment with a new persistent disk, but note that you will lose all data on the existing disk by taking this action, so please copy any data you still need to an external location before performing this action.
Please sign in to leave a comment.