Skip to content

Commit

Permalink
Merge pull request #1660 from opensafely/codespace-recovery-mode
Browse files Browse the repository at this point in the history
Explaining Codespaces recovery mode
  • Loading branch information
lucyb authored Oct 29, 2024
2 parents ad7e4d0 + fab0b42 commit f353a1e
Showing 1 changed file with 6 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,12 @@ This is perfectly normal and is a result of how we have configured Codespaces to
If you plan to use Stata in your project, then you will need to click the "Authorize and continue" button.
If you do not plan to use Stata, then you may click either button.

## My Codespace says it's in "recovery mode"

Occasionally when creating a Codespace something goes wrong. In these instances, GitHub will boot the Codespace into a "recovery mode". This provides you with a very basic environment in which to debug the problem. If this happens, either delete it and try again or contact tech support. If you contact tech support, then don't delete the Codespace, as it's likely you'll be asked for the creation logs so the problem can be investigated.

In recovery mode, you will not be able to access any of the usual tools or VS Code plugins. Some basic functionality, like copy and paste, may not work as expected either. So you should not attempt you use it for any work. GitHub provide some more information about Codespace recovery mode in their [documentation](https://docs.github.com/en/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces#codespace-creation-fails).

## R Session Error

After restarting a stopped Codespace in which you were using RStudio, you may see the following error:
Expand Down

0 comments on commit f353a1e

Please sign in to comment.