UTF-8 misclassified as binary at sample boundary
Cluster 81651. Data as of
Nothing open on GitHub. Fix merged in #81961 on 8 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #81961. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where the 1000-byte sample used for binary detection incorrectly flags valid UTF-8 files as binary when the sample boundary splits a multi-byte character. Fixes and reports span read_file, patch, and search_files tools.
Open issues0
Open PRs0
Fixes on record
-
#81961 fix(file-ops): stop flagging boundary-cut UTF-8 as binary across read_file/patch/search_files
files:
contributors/emails/[redacted:email],tests/tools/test_file_operations.py,tests/tools/test_read_file_utf8_binary_regression.py,tools/file_operations.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#81653 fix(tools): don't flag UTF-8 files as binary when the 1000-byte sample cut splits a multi-byte char · superseded by another PR →
#81961,#76924,#80440
Closed issues · 1
- Closed#81651Bug: read_file misclassifies valid UTF-8 text as binary when the 1000-byte sample cut lands mid-multibyte-character
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #81961
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 8 Aug 2026