-
Notifications
You must be signed in to change notification settings - Fork 1.3k
fix(tools): preserve non-UTF-8 bytes in StrReplaceFile edits #2594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
686f6c61
wants to merge
4
commits into
MoonshotAI:main
Choose a base branch
from
686f6c61:fix/2591-str-replace-preserve-binary-bytes
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
dd3dfc4
fix(tools): preserve non-UTF-8 bytes in StrReplaceFile edits
686f6c61 473b141
fix(tools): match CRLF when applying multi-line StrReplaceFile edits
686f6c61 4d385ef
fix(tools): reject empty old string in StrReplaceFile
686f6c61 169363a
fix(tools): count-dominant line endings in StrReplaceFile
686f6c61 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔴 Edits spanning multiple lines stop working on Windows-style text files
The file's stored line endings are now matched literally against the model-supplied text (
p.read_bytes()atsrc/kimi_cli/tools/file/replace.py:153) instead of being normalized first, so any edit spanning more than one line in a file saved with Windows line endings never matches and the edit is rejected.Impact: Users editing CRLF files (common on Windows or in repos with CRLF checkouts) get "No replacements were made" for every multi-line edit.
Newline normalization lost by switching from text read to raw byte read
Previously the file was read with
p.read_text(errors="replace"), which goes throughkaos.readtext(packages/kaos/src/kaos/local.py:116-125) using Python's default universal-newlines mode, so\r\nin the file became\nin memory and a model-providedoldcontaining\nmatched.The model only ever sees
\n, because ReadFile also iterates lines in text mode (src/kimi_cli/tools/file/read.py:181usesp.read_lines(...), universal newlines).Now
raw = await p.read_bytes()keeps\r\n, and_apply_edit_bytesencodesoldas UTF-8 (src/kimi_cli/tools/file/replace.py:97) and searches the raw stream, sob"foo\nbar"cannot matchb"foo\r\nbar"; the tool returns the "No replacements were made" error atsrc/kimi_cli/tools/file/replace.py:160-165.The same literal-byte matching also breaks edits containing non-ASCII characters in files stored in a non-UTF-8 encoding (e.g. GBK/latin-1), which the old lossy-decode path could at least partially match.
A fix would be to detect the file's dominant line ending (and/or try a CRLF-normalized variant of
old/new) before doing the byte-level search, while still writing back raw bytes.Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 473b141: StrReplaceFile now detects the file's dominant line ending (CRLF if any CRLF is present) and rewrites model-supplied
old/new(always LF) to match before the byte search, while still writing raw bytes so non-UTF-8 regions stay intact. Added regression tests for multi-line CRLF edits and CRLF + invalid UTF-8.