Forumics logo Forumics
Issue 01

Back to issue

All Cline known issues

CLAIM C058 Supported 2026-11-08

GitHub issue #13365 in cline/cline, opened 2026-08-19 by gaogage, records a report that clicking Generate Commit Message in the SCM panel fails with [Commit Generation Failed] stdout maxBuffer length exceeded whenever the diff output exceeds the Node default exec buffer of 1MB, that the diff calls in apps/vscode/src/utils/git.ts go through the promisified exec and execFile wrappers without a maxBuffer option, verified on current main and in the shipped v4.1.10 bundle, and that the later truncation to 500 lines and 5000 chars happens only after exec has already killed the child process, so collecting the full stdout just to discard most of it is what breaks the feature.

Verbatim Excerpts from Cited Records
“whenever the diff output exceeds Node's default `exec` buffer (1MB).”
— gaogage · cline/cline (issue 13365 opening body, Description section) · 2026-08-19T05:37:01Z ·GitHub Issue ↗
“In `apps/vscode/src/utils/git.ts` (verified on current `main` and in the shipped v4.1.10 bundle):”
— gaogage · cline/cline (issue 13365 opening body, Root cause section) · 2026-08-19T05:37:01Z ·GitHub Issue ↗
“- `git --no-pager diff --staged --diff-filter=d`, `git --no-pager diff HEAD`, and the per-untracked-file `git diff --no-index` calls all go through `execAsync` / `execFileAsync` **without a `maxBuffer` option**, so Node's 1MB default applies.”
— gaogage · cline/cline (issue 13365 opening body, Root cause section) · 2026-08-19T05:37:01Z ·GitHub Issue ↗
“- The diff is later truncated anyway (`fxn` caps at 500 lines, the commit-message prompt caps at 5000 chars), but that truncation happens **after** `exec` has already killed the child process — so collecting the full stdout just to discard most of it is what breaks the feature.”
— gaogage · cline/cline (issue 13365 opening body, Root cause section) · 2026-08-19T05:37:01Z ·GitHub Issue ↗
Counter-record: Closed 2026-11-07 by github-actions[bot] because the issue had been inactive for 14 days since being marked stale on 2026-10-22; the closure is an automated stale-close, not a fix confirmation, and no fix or maintainer response appears in the 3 comments read (all 3 read: the linear-code bot linkback to CLINE-3018, the stale notice, and the stale-close notice). No reproduction dispute appears in the surveyed thread. The claim documents only the original report, not a verified current state. Falsification probe: If issue 13365 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn. Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by scripts/verify_claim_verbatim.py.