Skip to content
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

6532025: GIF reader throws misleading exception with truncated images #96

Closed
wants to merge 1 commit into from

Conversation

@kvergizova
Copy link
Contributor

@kvergizova kvergizova commented Jan 28, 2021

I'd like to backport 6532025 to 13u for parity with 11u.
The patch applies cleanly.
Tested with tier1; new test fails without the patch, passes with it.


Progress

  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change must be properly reviewed

Issue

  • JDK-6532025: GIF reader throws misleading exception with truncated images

Download

$ git fetch https://git.openjdk.java.net/jdk13u-dev pull/96/head:pull/96
$ git checkout pull/96

@bridgekeeper
Copy link

@bridgekeeper bridgekeeper bot commented Jan 28, 2021

👋 Welcome back evergizova! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk openjdk bot changed the title Backport bd78beae15a497329be279e8754cca0c6b2249eb 6532025: GIF reader throws misleading exception with truncated images Jan 28, 2021
@openjdk
Copy link

@openjdk openjdk bot commented Jan 28, 2021

This backport pull request has now been updated with issue from the original commit.

@openjdk
Copy link

@openjdk openjdk bot commented Jan 28, 2021

@kvergizova This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

6532025: GIF reader throws misleading exception with truncated images

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@mlbridge
Copy link

@mlbridge mlbridge bot commented Jan 28, 2021

Webrevs

@kvergizova
Copy link
Contributor Author

@kvergizova kvergizova commented Jan 29, 2021

/integrate

@openjdk openjdk bot added the sponsor label Jan 29, 2021
@openjdk
Copy link

@openjdk openjdk bot commented Jan 29, 2021

@kvergizova
Your change (at version 6b8fdfd) is now ready to be sponsored by a Committer.

@yan-too
Copy link
Collaborator

@yan-too yan-too commented Jan 29, 2021

/sponsor

@openjdk
Copy link

@openjdk openjdk bot commented Jan 29, 2021

@yan-too @kvergizova Since your change was applied there have been 3 commits pushed to the master branch:

  • a27970f: 8243290: Improve diagnostic messages for class verification and redefinition failures
  • fd622d3: 8256809: Annotation processing causes NPE during flow analysis
  • 5c15783: 8212160: JVMTI agent crashes with "assert(_value != 0LL) failed: resolving NULL _value"

Your commit was automatically rebased without conflicts.

Pushed as commit 49b1754.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

@kvergizova kvergizova deleted the backport-6532025 branch Jan 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants