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

Avoid throwing an exception on close if a VertxInputStream is closed #18643

Merged
merged 1 commit into from
Jul 14, 2021

Conversation

essobedo
Copy link
Contributor

@essobedo essobedo commented Jul 13, 2021

Motivation

An IOException is thrown If we call close() on an instance of VertxInputStream that is already closed, while the Javadoc of a close states I quote:

If the stream is already closed then invoking this method has no effect.

Modifications

  • Changes the code to do nothing on close() if the stream is already closed on both existing VertxInputStream

@quarkus-bot
Copy link

quarkus-bot bot commented Jul 13, 2021

This workflow status is outdated as a new workflow run has been triggered.

Failing Jobs - Building 8f74923

Status Name Step Test failures Logs Raw logs
MicroProfile TCKs Tests Verify Test failures Logs Raw logs

Full information is available in the Build summary check run.

Test Failures

⚙️ MicroProfile TCKs Tests #

📦 tcks/microprofile-fault-tolerance

org.eclipse.microprofile.fault.tolerance.tck.TimeoutUninterruptableTest.testTimeoutAsyncBulkhead line 190 - More details - Source on GitHub

@geoand geoand merged commit 75a14d3 into quarkusio:main Jul 14, 2021
@quarkus-bot quarkus-bot bot added this to the 2.1 - main milestone Jul 14, 2021
@essobedo essobedo deleted the no-exception-on-close branch January 19, 2022 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants