{"version":"2.1.248","anchor":"oversized-git-check-attr-output-is-now-detected-instead-of-p","canonical_anchor":"oversized-git-check-attr-output-is-now-detected-instead-of-p","heading":"Oversized git check-attr output is now detected instead of parsed truncated","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/oversized-git-check-attr-output-is-now-detected-instead-of-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Oversized `git check-attr` output is now detected instead of parsed truncated\n\nTruncated git attribute output is now detected instead of being read as \"no attributes\".\n\n**What**\n\nThe helper that asks git whether a file has `filter`, `working-tree-encoding` or `ident` attributes returns a distinct `\"overflow\"` result when git's output exceeded the read buffer, rather than parsing a cut-off response and concluding the file has no attributes. This matters for deciding whether a file goes through git smudge\/clean filters before Claude Code edits it.\n\n**Evidence**\n\n`if (d.maxBufferExceeded) return \"overflow\";`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}