-
Notifications
You must be signed in to change notification settings - Fork 541
8282134: Certain regex can cause a JS trap in WebView #739
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
Conversation
|
👋 Welcome back jaybhaskar! A progress list of the required criteria for merging this PR into |
Webrevs
|
|
/reviewers 2 |
|
@kevinrushforth |
kevinrushforth
left a comment
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.
The fix looks good. I confirm that the new test fails without the fix and passes with the fix.
|
|
@jaybhaskar This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 9 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@kevinrushforth, @arapte) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
|
|
git commit -c user.name='Preferred Full Name' --allow-empty -m 'Update full name' fatal: Option -m cannot be combined with -c/-C/-F. |
a041e77 to
3fad1fc
Compare
|
Author name Change , due to bot comment $ git checkout public-sec-bug |
|
In general, we prefer that you not force push your branch once the associated PR is under review. In this case, it seems that an incorrect Skara message led you to amend the existing commit, rather than adding a new empty commit as intended. I'll file a bug against Skara. |
|
/integrate |
|
@jaybhaskar |
|
/sponsor |
|
Going to push as commit 7396396.
Your commit was automatically rebased without conflicts. |
|
@kevinrushforth @jaybhaskar Pushed as commit 7396396. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Fix YarrJIT backtrackCharacterClassNonGreedy breakpoint() Certain regex can cause a JS trap in WebView
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jfx pull/739/head:pull/739$ git checkout pull/739Update a local copy of the PR:
$ git checkout pull/739$ git pull https://git.openjdk.java.net/jfx pull/739/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 739View PR using the GUI difftool:
$ git pr show -t 739Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jfx/pull/739.diff