-
Notifications
You must be signed in to change notification settings - Fork 54
patch: improve validation of ed diffs #968
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
Conversation
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
Contributor
mknos
commented
Feb 26, 2025
- Make more of an effort to reject patches where line addresses are not valid
- Reading over the ed command parser in Patch::Ed::apply(), the regex assignment was not always correct
- test1: invalid command "19,0d" was incorrectly interpreted as (valid) "19,19d" thanks to the '||' operator
- test2: "19,18d" command was accepted, but the range is backwards
- test3: "0,19d" command was accepted, but address 0 is not allowed for "d"
- test4: "0,19c" command was accepted, but address 0 is not allowed for "c"
- I tested this by skipping to PLAN_J, using a diff with an update on line1 (ed command 0a is valid and means append after line 0)
- Modifying elements of the diff input, I could trigger the new validation errors
* Make more of an effort to reject patches where line addresses are not valid * Reading over the ed command parser in Patch::Ed::apply(), the regex assignment was not always correct * test1: "19,0d" command was incorrectly interpreted as "19,19d" thanks to the '||' operator * test2: "19,18d" command was accepted, but the range is backwards * test3: "0,19d" command was accepted, but address 0 is not allowed for "d" * test4: "0,19c" command was accepted, but address 0 is not allowed for "c" * I tested this by skipping to PLAN_J, using a modified diff with an update on line1 (ed command 0a is valid and means append after line 0) * Modifying elements of the diff input, I could trigger the new validation errors %perl diff -e env env2 | perl tee env.diff 19,20d 5,8c META DATA AND MORE . 0a #NEW LINE 1!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! .
Pull Request Test Coverage Report for Build 13535808664Details
💛 - Coveralls |
Owner
|
changes: reject patches where the range is not valid |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Program: patch
The patch program
Status: released
there is a new release with this fix
Type: bug
an existing feature does not work
Type: enhancement
improve a feature that already exists
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.