-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Fix handling of PTYs when renderer is reloaded #4346
Conversation
- Persist processes if error code is "GoingAway" - Switch the shell websocket handling to use v8's serialization functions and full objects instead of Base64 and single character channel names. This should help readability of the code. - Add documentation for WebSocketApiParams Signed-off-by: Jari Kolehmainen <jari.kolehmainen@gmail.com> Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
@jim-docker Fixed. |
I'm still seeing unresponsive terminals. I open 3 terminals, disconnect/reconnect the cluster and one or two of them just have a blinking cursor (no prompt, don't take input). I can see "Connecting.." flash briefly and then just the cursor. |
logs indicate that the session is resumed (always see this for each terminal) |
Will investigate |
Why not just kill all the terminal processes upon cluster disconnect? |
That should already be happening, but that isn't what the problem is. |
- Shell sessions are now not persisted if the cluster is disconnected - On reconnect, fake the last data message being sent so that the terminal is not empty Signed-off-by: Sebastian Malton <sebastian@malton.name>
… killed Signed-off-by: Sebastian Malton <sebastian@malton.name>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All issues I found are fixed
Persist processes if error code is "GoingAway"
Switch the shell websocket handling to use v8's serialization
functions and full objects instead of Base64 and single character
channel names. This should help readability of the code.
Add documentation for WebSocketApiParams
Signed-off-by: Jari Kolehmainen jari.kolehmainen@gmail.com
Signed-off-by: Sebastian Malton sebastian@malton.name
fixes #4318