Remove an excessive close after the abort call in S3RangeReader #3324
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR addresses the issue that happens on newer JVMs (it happened to me after upgrading up to
AdoptOpenJDK 1.8.0_275
from1.8.0_265
). I'm surprised that this issue is JVM specific. This PR finishes #3079 and adds explanations of theabort()
function behavior.This PR also converts #3239 into a less pressing issue.
Checklist
docs
guides update, if necessaryDemo
Without this PR the code snippet above fails with the following error: