From 19b5efec3ab57fc3ebfb285b8c7ad623c0f92abb Mon Sep 17 00:00:00 2001 From: "itarun.p" Date: Mon, 3 Aug 2026 15:17:40 +0700 Subject: [PATCH] chore(usage): escape the raw NUL bytes in jsonl-parser.ts as \0 The file held 4 raw NUL bytes: 2 are the Map-key separators in template literals (offsets 7260, 7365) and 2 sit in the comment describing them (5708, 5745). Git classifies a blob binary when it finds a NUL in the first 8000 bytes, so it was the COMMENT's NUL that tripped the check and suppressed the file's diff entirely -- including from the repo's own audit greps, which then returned 0 matches as a false negative. `\0` in a TypeScript template literal produces the same U+0000 character, so this is a source-encoding change with no runtime effect. Verified by undoing the escape and comparing: it reproduces the previous blob byte-for-byte. Split out as its own commit deliberately. GitHub sniffs the PRE-image when deciding binary-vs-text and does not apply the head tree's .gitattributes -- measured on an earlier revision of this branch, where the commits API reported no patch for this file even though .gitattributes was present in the same tree. Landing the escape separately gives the following commit a NUL-free pre-image, which is what GitHub actually looks at. This commit's own diff still renders as binary. It is 4 bytes; `git show -- src/usage/jsonl-parser.ts` or the round-trip check above settles it. --- src/usage/jsonl-parser.ts | Bin 8052 -> 8056 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/src/usage/jsonl-parser.ts b/src/usage/jsonl-parser.ts index 895e0c8a56552d1bdbebbd61e34ac99fd95e7bd3..8e58dff09d6d76bfd97787dd14b2d72c22cf2ea3 100644 GIT binary patch delta 37 ncmexj_rq?3j~G*o!DL@C6(F^_NbD6Wh#M=D0pcE$S;qtb{PYa4 delta 33 mcmexi_r-35j~FAvWIr(#MuyELVy{?%oCKK+Am^0KIwk