-
Notifications
You must be signed in to change notification settings - Fork 182
partly inline read_response, fix body stream leak #696
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
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
62fba89
partly inline Client.read_response
79d4287
read_body does not need to wrap result in Lwt.t
1329d4d
untangle finalising maze in read_body
a3c8a35
no need to drain the body in callv anymore
a218e37
Don't use Gc.finalise for closing fd or consuming stream
feb2775
add comment about Lwt.on_success an GC
384fa05
Add closefn where it is needed
dinosaure 68c74db
Re-use Lwt.on_cancel/on_failure on our flow to properly close the con…
dinosaure File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
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.
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.
Does this mean that if we fail due to an exception or maybe a timeout that cancels the thread, this will automatically leak the stream?
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.
That's what I initially suspected because I thougt
Lwt.on_successwill hold a reference onstream. But this is not true. It is the other way round.streamholds a callback to theLwt.on_successmachinery. So the GC will be able to collectstream.Uh oh!
There was an error while loading. Please reload this page.
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.
Oh, I see, thanks. This explains why while testing I was not noticing any regression.
Can you add a comment about it on this line?