Skip to content

fix: permit SSH by default when startup script fails #6798

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 27, 2023
Merged

fix: permit SSH by default when startup script fails #6798

merged 1 commit into from
Mar 27, 2023

Conversation

ammario
Copy link
Member

@ammario ammario commented Mar 25, 2023

No description provided.

@ammario ammario requested a review from kylecarbs March 25, 2023 17:50
@ammario ammario enabled auto-merge (squash) March 25, 2023 17:50
@ammario ammario merged commit b439c3e into main Mar 27, 2023
@ammario ammario deleted the ssh-fix branch March 27, 2023 15:00
@github-actions github-actions bot locked and limited conversation to collaborators Mar 27, 2023

// We don't want to fail on a startup script error because it's
// natural that the user will want to fix the script and try again.
// We don't print the error because cliui.Agent does that for us.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ammario with this change, there'll be no indication for people SSH:ing in that there's a problem or that the workspace ran into an error (--stdio).

The logs would only be visible by doing ssh -v.

I guess one option would be to print this on the agent side, as part of MOTD.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MOTD makes sense to me

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants