-
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
8279283 - BufferedInputStream should override transferTo #6935
Conversation
👋 Welcome back mkarg! A progress list of the required criteria for merging this PR into |
Webrevs
|
BIS is not specified to be thread safe but the existing read/write operations are. If transferTo is overridden then this is an area that will require close attention. Have you surveyed the existing tests to see if transferTo is invoked on a BIS? New tests may be needed. |
In analogy to the other read/write operations I now have synchronized transferTo in 8dac240 to be on the safe side.
Did not find an existing test for BIS.transferTo, so I will write a new test for this. |
I have provided a test for BIS.transferTo in fbc5def. |
Maybe we need to include into this patch the benchmark referenced to in the body of the ticket? |
I think you'll need to look at the interaction with mark/reset. I don't think you can bypass the buffering when there is a mark set. |
Good catches, I will look into your comments! |
@mkarg This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
Please keep open, still working on it. |
@mkarg This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
Please keep this PR open; I will continune work on it soon. |
@mkarg This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
Please keep this PR open; I will continune work on it soon. |
@mkarg This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
Please keep this PR open; I will continune work on it soon. |
Can this PR be closed or returned to daft? |
I think we should turn it back to draft. |
@mkarg This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
Please keep this PR open; I will continune work on it soon. |
@mkarg This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
@mkarg This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the |
Will this be reopened somewhen? The proposed changes seems useful |
@bplb Fixed the issues you pointed out. Kindly requesting approval. :-) |
I don't have any more comments, the recent test cleanups are good. I assume @bplb will sponsor. |
Thanks a lot for all your kind help with this PR! :-) |
@AlanBateman Kindly asking for |
|
@mkarg 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 263 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. 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 (@bplb) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@bplb I would be very glad if you would |
/sponsor |
Done. |
Going to push as commit 7515b30.
Your commit was automatically rebased without conflicts. |
@AlanBateman I opened another PR to continue this discussion. |
Implementation of JDK-8279283
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/6935/head:pull/6935
$ git checkout pull/6935
Update a local copy of the PR:
$ git checkout pull/6935
$ git pull https://git.openjdk.org/jdk pull/6935/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 6935
View PR using the GUI difftool:
$ git pr show -t 6935
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/6935.diff