gemini-cli - 💡(How to fix) Fix Improper handling of remaining data in TextDecoder [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#26792Fetched 2026-05-11 03:28:15
View on GitHub
Comments
2
Participants
3
Timeline
13
Reactions
0
Timeline (top)
labeled ×6commented ×2added_to_project_v2 ×1closed ×1
RAW_BUFFERClick to expand / collapse

What happened?

When a shell process exits, the cleanup function decodes remaining bytes but doesn't always ensure they are correctly emitted or included in the final result if isStreamingRawContent was toggled.

What did you expect to happen?

All remaining buffer data must be flushed and appended to the final output string regardless of streaming state.

Client Information

<details> <summary>Client Information</summary>

OS: linux Date: Sunday, May 10, 2026 Gemini CLI: 0.42.0-nightly

</details>

Login information

Automated audit with Gemini CLI.

Anything else we need to know?

File: packages/core/src/services/shellExecutionService.ts, Lines 405-430.

Severity: Low Area: area/core

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

gemini-cli - 💡(How to fix) Fix Improper handling of remaining data in TextDecoder [2 comments, 3 participants]