INTEGRATION [PR#578 > development/8.1] Bugfix/zenko 1197/s3 data leak #580
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When receiving this callback, sometimes the socket is already closed (e.g. upon RST) but sometimes we have to cloud it ourselves.
When the underlying socket of the dataStream is closed this is not considered as a stream error. So we have to hook the event and do the cleanup by ourselves
…bugfix/ZENKO-1197/s3-data-leak
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request has been created automatically.
It is linked to its parent pull request #578.
Do not edit this pull request directly.
If you need to amend/cancel the changeset on branch
w/8.1/bugfix/ZENKO-1197/s3-data-leak, please follow thisprocedure:
$ git fetch $ git checkout w/8.1/bugfix/ZENKO-1197/s3-data-leak $ # <amend or cancel the changeset by _adding_ new commits> $ git push origin w/8.1/bugfix/ZENKO-1197/s3-data-leakPlease always comment pull request #578 instead of this one.