You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 3, 2022. It is now read-only.
If the user adds some bad commands in startup.sh, the run script will exit prematurely, without starting the Datalab server, which means datalab connect will fail. We should handle these errors gracefully and maybe show an alert on the tree page saying some steps did not complete in the startup script.
I also experienced that just now. I noticed the datalab instance just kept on restarting. I tried deleting the startup.sh script but it just kept on coming back. In the end I had to delete the VM.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If the user adds some bad commands in startup.sh, the run script will exit prematurely, without starting the Datalab server, which means
datalab connect
will fail. We should handle these errors gracefully and maybe show an alert on the tree page saying some steps did not complete in the startup script.This is originally an SO question here.
The text was updated successfully, but these errors were encountered: