-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8155902: DataOuputStream should clarify that it might write primitive types as multiple byte groups #14791
Conversation
It might be equally reasonable simply to resolve the issue as "Not an Issue." A CSR will be created if that is not the case. |
👋 Welcome back bpb! A progress list of the required criteria for merging this PR into |
Webrevs
|
This issue is reported against JDK 8 and 9. It was fixed in 16 with 17f04fc. I think you can close it as duplicate. |
Thanks. I saw that change go by but did not connect the dots. Was it actually verified that things are not split up into two or more packets? It seems that |
Yes, the test case included in JBS sends all 4 bytes in a single packet now. |
/csr |
@bplb has indicated that a compatibility and specification (CSR) request is needed for this pull request. @bplb please create a CSR request for issue JDK-8155902 with the correct fix version. This pull request cannot be integrated until the CSR request is approved. |
In passing, we should probably look into the inconsistency in the synchronization. The write methods are synchronized, the writeXXX methods and other methods are not. The class specified that it is not safe for use by concurrent threads without appropriate synchronization. |
This can be addressed in the context of JDK-8295797. |
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.
LGTM.
@bplb 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 51 new 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 this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
/integrate |
Going to push as commit ed9337e.
Your commit was automatically rebased without conflicts. |
Add a disclaimer to
java.io.DataOutputStream
to the effect that it makes no guarantee as to how the underlying output stream actually writes the bytes provided to it.Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/14791/head:pull/14791
$ git checkout pull/14791
Update a local copy of the PR:
$ git checkout pull/14791
$ git pull https://git.openjdk.org/jdk.git pull/14791/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 14791
View PR using the GUI difftool:
$ git pr show -t 14791
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/14791.diff
Webrev
Link to Webrev Comment