Sweep: Edit fails to parse some messages with invalid TOML #81
Conversation
This file contains 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
|
No way this is correct |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This pull request addresses an issue where the
applyfunction inpatch.pyfails to correctly parse messages that contain invalid TOML due to unescaped backslashes. By adding an extra line of code, we ensure that all backslashes are properly escaped, thus preventing parsing errors and improving the robustness of the patch application process.Summary
gptme/tools/patch.pywhere unescaped backslashes in the input could lead to invalid TOML parsing errors.applyfunction to replace single backslashes (\) with double backslashes (\\), ensuring proper escaping.Fixes #71.
馃帀 Latest improvements to Sweep:
馃挕 To get Sweep to edit this pull request, you can:
This is an automated message generated by Sweep AI.