Repository navigation
Update RStudio server (& python venv) - #1113
Merged
Merged
Conversation
(Not sure why this didn't cause other trouble!)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes https://github.com/AlexsLemonade/rstudio-server/issues/219
Here I am updating the version of RStudio that we use to a version with the fix for rstudio/rstudio#17440, which has been tripping us up (understatement) during training. This should resolve our crashing issue (though we won't know for a bit).
This version includes Posit assistant UI (though it isn't installed), but I disabled it at the server level.
While preparing this, I ran into some
renvissues during builds, which are fixed by a few small package updates.I also hit a new python install error, so I decided to resolve it by implementing a venv installation, with setting environment variables to make sure that user paths (other than root) are set to use it.
So this also closes #885
My plan is to test this in
edgefor a bit, and then possibly replace the2026-octoberdocker image with it for people working on our server. I don't think there is much need to replace earlier docker images, but the October one seems worth doing, since it is most likely to have active users. I can do this all at the Dockerhub level rather than requiring a rerelease on GitHub, or we could rerelease on GitHub...