Description
Bug description
It can be hard to notice that your dotfiles script is failing suddenly. In order to inspect $HOME/.dotfiles.log
, it's necessary to at least have the IDE start but if you have a relatively complex dotfiles installation script and it fails, it can sometimes cause the IDE to not start.
Steps to reproduce
- In your dotfiles script, do something like
sudo rm -rf /ide
Workspace affected
No response
Expected behavior
The loading splash screen to show an error if the dotfiles installation script fails, the user may acknowledge this by pressing an button to continue loading the workspace.
It might be also nice to have an extra button on the loading screen to view dotfiles.log
in case the dotfiles installation script didn't return an error code for users with dotfiles.
Example repository
No response
Anything else?
I experienced this myself several times.
Also a report internally on slack.
Related: #12100
Metadata
Metadata
Assignees
Labels
Type
Projects
Status