fix(cli): persist diagnostics before dead-terminal exits#2088
Open
Heyu2002 wants to merge 4 commits into
Open
Conversation
🦋 Changeset detectedLatest commit: 7465ca2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issue
Terminal execution abnormal termination #2045
Problem
When
stdoutorstderrreports a dead-terminal error such asEIOorEPIPE, the TUI restores the terminal and immediately exits with code 129.Because the exit is immediate, diagnostics written through buffered output or asynchronous logging may be lost. This leaves insufficient durable context to determine whether an observed session termination was caused by a task failure, a terminal stream failure, or another exit path.
What changed
stdoutEIO,stderrEPIPE, unrelated stream errors, diagnostic callback failures, captured context, and log ordering.@moonshot-ai/kimi-code.The existing emergency-exit behavior is intentionally unchanged. No documentation update is needed because this change adds internal diagnostics without introducing new commands, configuration, or user-facing workflows.
Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.