#20411 fix Yaml parsing for very long quoted strings #21279
Merged
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
stof
requested changes
Jan 13, 2017
| { | ||
| $longStringWithQuotes = str_repeat("x\r\n\\\"x\"x", 1000); | ||
|
|
||
| $yamlString = Inline::dump(['longStringWithQuotes' => $longStringWithQuotes]); |
There was a problem hiding this comment.
the short array syntax does not work on PHP 5.3, which is still supported by Symfony 2.7. Please change it.
There was a problem hiding this comment.
Sorry, good point.
I've pushed a new version.
|
👍 (once the PHP 5.3 compat is fixed of course) |
RichardBradley
force-pushed
the
ticket_20411
branch
from
100a0ce
to
51bca66
Compare
stof
approved these changes
Jan 13, 2017
|
Thank you @RichardBradley. |
xabbuh
added a commit
that referenced
this pull request
Jan 14, 2017
…ardBradley) This PR was merged into the 2.7 branch. Discussion ---------- #20411 fix Yaml parsing for very long quoted strings | Q | A | ------------- | --- | Branch? | 2.7 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #20411 | License | MIT | Doc PR | no This fixes #20411, a YAML string with too many backslash escapes can trigger a `PREG_BACKTRACK_LIMIT_ERROR` error in the Yaml parser. There should be no behavioural change other than the bug fix I have included a test which fails before this fix and passes after this fix. Commits ------- 51bca66 #20411 fix Yaml parsing for very long quoted strings
Merged
This was referenced Feb 6, 2017
Merged
Merged
Merged
fabpot
added a commit
that referenced
this pull request
Mar 17, 2017
…ardBradley) This PR was squashed before being merged into the 2.7 branch (closes #21523). Discussion ---------- #20411 fix Yaml parsing for very long quoted strings | Q | A | ------------- | --- | Branch? | 2.7 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #20411 | License | MIT | Doc PR | no This is a second fix for the issue discussed in #20411. My first PR (#21279) didn't fix the bug in all cases, sorry. If a YAML string has too many spaces in the value, it can trigger a `PREG_BACKTRACK_LIMIT_ERROR` error in the Yaml parser. There should be no behavioural change other than the bug fix I have included a test which fails before this fix and passes after this fix. I have also added checks that detect other PCRE internal errors and throw a more descriptive exception. Before this patch, the YAML engine would often give incorrect results, rather than throwing, on a PCRE `PREG_BACKTRACK_LIMIT_ERROR` error. Commits ------- c9a1c09 #20411 fix Yaml parsing for very long quoted strings
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.
This fixes #20411, a YAML string with too many backslash escapes can trigger a
PREG_BACKTRACK_LIMIT_ERRORerror in the Yaml parser.There should be no behavioural change other than the bug fix
I have included a test which fails before this fix and passes after this fix.