Repository navigation
fix: accept cross-model arg aliases in str_replace_editor (Qwen etc.) #4
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
Merged
Merged
Changes from all commits
Commits
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
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
Oops, something went wrong.
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.
When a caller supplies both spellings with
new_str: nulland a non-nullnew_string, this condition replaces the canonical value with the alias despite the stated canonical-wins behavior. An explicit null is valid and meaningful forstr_replacebecauseEditTool.str_replaceconverts it to an empty string to delete the matched text; the current mapping instead inserts the alias text and can silently produce the wrong document.Useful? React with 👍 / 👎.
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.
Acknowledged, but I'm leaving the mapping as-is — the failure mode is effectively unreachable and the strict fix has real downsides.
new_str: null(delete the matched text) and a non-nullnew_string(replace with that text). A model uses one spelling or the other; it doesn't emit a self-contradicting call, so there's no real (Qwen or otherwise) behavior that reaches this branch.str_replace,nulland""are already equivalent —EditTool.str_replacecoercesNone→""— so the "wrong document" outcome only exists inside that contradictory call.None, sois Nonecan't distinguish "explicitly null" from "omitted". Doing it properly needs a sentinel default (_UNSET) on anOptional[str]param, which muddies the auto-generated JSON schema and validation for a case that can't occur.Net: the alias only kicks in when the canonical value is absent, which is the intended behavior for every real call. Happy to revisit if a concrete tool call is observed that actually sends both keys.