-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8244706: GZIP "OS" header flag hard-coded to 0 instead of 255 (RFC 1952 non-compliance) #130
Conversation
👋 Welcome back jpai! A progress list of the required criteria for merging this PR into |
@jaikiran The following label will be automatically applied to this pull request: When this pull request is ready to be reviewed, an RFR email will be sent to the corresponding mailing list. If you would like to change these labels, use the |
Webrevs
|
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.
Hi Jaikiran,
The change seems fine an inline with the RFC. I can sponsor this once we have another review.
I have run the JCK tests for Zip/Gzip/Jar and Mach5 JDK tier1, tier2 and tier3
@jaikiran This change now passes all automated pre-integration checks. In addition to the automated checks, the change must also fulfill all project specific requirements After integration, the commit message will be:
Since the source branch of this PR was last updated there have been 53 commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid automatic rebasing, please merge As you do not have Committer status in this projectan existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@LanceAndersen, @bchristi-git) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
Thank you Lance for the review and running the tests. I'll wait for another review before initiating the integrate command. |
Mailing list message from Joe Darcy on core-libs-dev: Should issue have a CSR review for the behavior change? -Joe On 9/12/2020 7:25 PM, Jaikiran Pai wrote: |
Mailing list message from Lance Andersen on core-libs-dev: Hi Joe, I guess it could. Given it is not used within the implementation(or defined outside of the spec), I will defer to you preference :-)
Best Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037 |
Mailing list message from Joe Darcy on core-libs-dev: Hi Lance, I'd prefer to err on the side of having a CSR; thanks, -Joe On 9/14/2020 3:55 PM, Lance Andersen wrote:
|
Mailing list message from Lance Andersen on core-libs-dev: Hi Joe, Ok, will create one tomorrow. Best
Best Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037 |
…52 non-compliance) Reviewed-By:
I received some useful suggestions, offline, from Lance and Brent on this change and have updated this PR to include those suggestions. Please ignore the intermediate commits though (I accidentally added an unwanted file to this PR, which I have then removed in a subsequent commit). This is ready for a review now. |
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.
Reviewed. Thanks for reworking the change into the existing out.write() call.
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.
Thank you for making the changes that Brent and I suggested. This looks good. I have submitted, a CSR to track the change.
I have also created a Release Note as well.
Once the CSR has been approved, I will sponsor your change
Thank you Lance for taking care of the CSR and the release notes. Given that the CSR has been approved, I'm initating the integrate command. /integrate |
/sponsor |
@LanceAndersen @jaikiran Since your change was applied there have been 53 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit e5866aa. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
…larifications around DistributedSubjectCombiner purpose. openjdk#130
Can I please get a review and a sponsor for this patch which fixes the issue reported in https://bugs.openjdk.java.net/browse/JDK-8244706?
The commit here sets the
OS
header flag to255
(which representsunknown
) as noted in [1]. A new test has been included in this commit to verify the change. Furthermore, this doesn't impact thejava.util.zip.GZIPInputStream
since it ignores [2] this header value while reading the headers from the stream.[1] https://tools.ietf.org/html/rfc1952#page-7
[2] https://github.com/openjdk/jdk/blob/master/src/java.base/share/classes/java/util/zip/GZIPInputStream.java#L173
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/130/head:pull/130
$ git checkout pull/130