Skip to content

console: CNS-38 explain why an interrupted shell command needs a retry - #38610

Open
jdonelson wants to merge 1 commit into
mainfrom
jdonelson/CNS-38_disconnect-retry-err-msg
Open

console: CNS-38 explain why an interrupted shell command needs a retry#38610
jdonelson wants to merge 1 commit into
mainfrom
jdonelson/CNS-38_disconnect-retry-err-msg

Conversation

@jdonelson

@jdonelson jdonelson commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Motivation

Fixes CNS-38

Instead of simply displaying "Retry" after a disconnection, add an error message.

Description

Investigation revealed that we can mitigate the disconnection problem at its source. This UX improvement is a first step.
Screenshot 2026-09-01 at 4 19 47 PM

Verification

New test case asserting CONNECTION_CLOSED mid-command sets both interrupted and the error. This event had no coverage at all before.

Assert that an interrupted command renders the message and an enabled Retry button, and that a normal command renders neither.

Manually tested with a non-trivial bit of chicanery.

@jdonelson
jdonelson requested a review from a team as a code owner September 1, 2026 20:58
@jdonelson
jdonelson requested a review from leedqin September 1, 2026 20:58
@linear-code

linear-code Bot commented Sep 1, 2026

Copy link
Copy Markdown

CNS-38

@leedqin leedqin left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

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.

2 participants