From d7653d9f689329aa27b1360cda4a93867399e97f Mon Sep 17 00:00:00 2001 From: Ammar Date: Wed, 15 Oct 2025 22:17:41 -0500 Subject: [PATCH] =?UTF-8?q?=F0=9F=A4=96=20Reduce=20git=20status=20console?= =?UTF-8?q?=20spam=20for=20output=20overflow?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Filter out OUTPUT TRUNCATED and OUTPUT OVERFLOW errors from console.debug logging in GitStatusStore. These errors are common in large repositories and are handled gracefully by the system, so logging them just adds noise. The git status script already has proper overflow handling via overflow_policy, so these messages provide no actionable information to users. --- src/stores/GitStatusStore.ts | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/stores/GitStatusStore.ts b/src/stores/GitStatusStore.ts index 31a880dcc..578fe8721 100644 --- a/src/stores/GitStatusStore.ts +++ b/src/stores/GitStatusStore.ts @@ -219,7 +219,13 @@ export class GitStatusStore { } if (!result.data.success) { - console.debug(`[gitStatus] Script failed for ${metadata.id}:`, result.data.error); + // Don't log output overflow errors at all (common in large repos, handled gracefully) + if ( + !result.data.error?.includes("OUTPUT TRUNCATED") && + !result.data.error?.includes("OUTPUT OVERFLOW") + ) { + console.debug(`[gitStatus] Script failed for ${metadata.id}:`, result.data.error); + } return [metadata.id, null]; }