Skip to content

Terminal exit error handling - #116

Closed
juliusmarminge wants to merge 1 commit into
mainfrom
cursor/terminal-exit-error-handling-eafe
Closed

Terminal exit error handling#116
juliusmarminge wants to merge 1 commit into
mainfrom
cursor/terminal-exit-error-handling-eafe

Conversation

@juliusmarminge

@juliusmarminge juliusmarminge commented Feb 28, 2026

Copy link
Copy Markdown
Member

Auto-close the terminal on exit and suppress benign write errors that occur during shutdown.

Commands like exit should gracefully close the terminal without displaying error messages, treating such "failures" as normal terminal behavior rather than hard errors.


Open in Web Open in Cursor 

Note

Handle terminal exit errors by invoking components.TerminalViewportProps.onCloseTerminal from components.TerminalViewport and remove system messages in ThreadTerminalDrawer.tsx

Add onCloseTerminal to components.TerminalViewportProps and call it when write errors match terminal-errors.isIgnorableTerminalWriteError or on exited; update ThreadTerminalDrawer to pass the callback; add tests for isIgnorableTerminalWriteError and implement the utility in terminal-errors.ts.

📍Where to Start

Start with the TerminalViewport component changes in ThreadTerminalDrawer.tsx, then review isIgnorableTerminalWriteError in terminal-errors.ts.

Macroscope summarized 7dc0ff1.

Co-authored-by: Julius Marminge <juliusmarminge@users.noreply.github.com>
@cursor

cursor Bot commented Feb 28, 2026

Copy link
Copy Markdown
Contributor

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

@coderabbitai

coderabbitai Bot commented Feb 28, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch cursor/terminal-exit-error-handling-eafe

Comment @coderabbitai help to get the list of available commands and usage tips.

radroid added a commit to radroid/t3code that referenced this pull request Aug 8, 2026
…eep reopened

Fallout from #56, caught by re-checking the alert list after it merged rather than assuming the count only goes down.

Before the sweep the tree had one nanoid@3.3.12, and GHSA pingdotgg#115/pingdotgg#116 against it sat auto-dismissed by GitHub's auto-triage rule — it was scoped as a development dependency. astro 7.2.0 restructured its tree, adding an already-fixed nanoid@3.3.17 alongside the old copy and flipping that copy's scope to runtime, which took it out from under the rule and reopened both alerts.

The sweep did not introduce a vulnerability — 3.3.12 was there before and was always affected — but it turned a suppressed finding into a live one.

One override, "nanoid@3": ^3.3.17, dedupes onto the version already in the tree. Both advisories want <= 3.3.17, so this clears both.

Ledger figures refreshed in the same commit per SEAMS.md's self-reference rule.
github-actions Bot pushed a commit to radroid/t3code that referenced this pull request Aug 10, 2026
…eep reopened

Fallout from #56, caught by re-checking the alert list after it merged rather than assuming the count only goes down.

Before the sweep the tree had one nanoid@3.3.12, and GHSA pingdotgg#115/pingdotgg#116 against it sat auto-dismissed by GitHub's auto-triage rule — it was scoped as a development dependency. astro 7.2.0 restructured its tree, adding an already-fixed nanoid@3.3.17 alongside the old copy and flipping that copy's scope to runtime, which took it out from under the rule and reopened both alerts.

The sweep did not introduce a vulnerability — 3.3.12 was there before and was always affected — but it turned a suppressed finding into a live one.

One override, "nanoid@3": ^3.3.17, dedupes onto the version already in the tree. Both advisories want <= 3.3.17, so this clears both.

Ledger figures refreshed in the same commit per SEAMS.md's self-reference rule.
radroid added a commit to radroid/t3code that referenced this pull request Aug 10, 2026
…eep reopened

Fallout from #56, caught by re-checking the alert list after it merged rather than assuming the count only goes down.

Before the sweep the tree had one nanoid@3.3.12, and GHSA pingdotgg#115/pingdotgg#116 against it sat auto-dismissed by GitHub's auto-triage rule — it was scoped as a development dependency. astro 7.2.0 restructured its tree, adding an already-fixed nanoid@3.3.17 alongside the old copy and flipping that copy's scope to runtime, which took it out from under the rule and reopened both alerts.

The sweep did not introduce a vulnerability — 3.3.12 was there before and was always affected — but it turned a suppressed finding into a live one.

One override, "nanoid@3": ^3.3.17, dedupes onto the version already in the tree. Both advisories want <= 3.3.17, so this clears both.

Ledger figures refreshed in the same commit per SEAMS.md's self-reference rule.
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