Skip to content
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

Reconnect terminal if websocket was closed #1858

Merged
merged 1 commit into from Dec 15, 2017

Conversation

gtritchie
Copy link
Member

Fixes #1844

If the terminal websocket gets closed (seeing this happen in container scenarios), mark the terminal as disconnected so the reconnection logic kicks in. For example, terminal should reconnect if the user types in the disconnected terminal.

Prior to this fix, the terminal would remain inactive and ignore input in this scenario.

Fixes #1844

If the websocket was closed (seeing this happen in container scenarios), mark the terminal as disconnected so the reconnection logic kicks in. For example, terminal should reconnect if the user types in the disconnected terminal.

Prior to this fix, the terminal would remain inactive and ignore input if the underlying websocket had closed.
@jmcphers jmcphers merged commit ff728a3 into master Dec 15, 2017
@jmcphers
Copy link
Member

Great, glad that was relatively straightforward to fix! Given that this fix looks pretty low-risk and addresses a terminal issue likely to be seen in the wild, how would you feel about backporting it to 1.1-patch?

@jmcphers jmcphers modified the milestone: v1.1-patch Dec 15, 2017
@gtritchie gtritchie deleted the bugfix/terminal-reconnect branch December 15, 2017 21:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Terminal disconnects when running server in Docker
2 participants