-
Notifications
You must be signed in to change notification settings - Fork 13k
Unhandled AbortError crash during stream generation in processTurn #21122
Copy link
Copy link
Closed
Labels
area/coreIssues related to User Interface, OS Support, Core FunctionalityIssues related to User Interface, OS Support, Core Functionalityhelp wantedWe will accept PRs from all issues marked as "help wanted". Thanks for your support!We will accept PRs from all issues marked as "help wanted". Thanks for your support!priority/p2Important but can be addressed in a future release.Important but can be addressed in a future release.status/possible-duplicatetype/bug
Metadata
Metadata
Assignees
Labels
area/coreIssues related to User Interface, OS Support, Core FunctionalityIssues related to User Interface, OS Support, Core Functionalityhelp wantedWe will accept PRs from all issues marked as "help wanted". Thanks for your support!We will accept PRs from all issues marked as "help wanted". Thanks for your support!priority/p2Important but can be addressed in a future release.Important but can be addressed in a future release.status/possible-duplicatetype/bug
Type
Fields
Give feedbackNo fields configured for issues without a type.
What happened?
When using the
gemini-cli, the application unexpectedly crashes with an unhandledAbortError.Stack Trace:
What did you expect to happen?
The CLI should catch the AbortError (or signal.aborted state) during the asynchronous stream processing.
tead of crashing the entire Node.js process with an unhandled rejection, it should handle the interruption gracefully.
Client information
Client Information
Run
geminito enter the interactive CLI, then run the/aboutcommand.Login information
Google Account
Anything else we need to know?
.