fix(ext/node): close upgraded socket when the underlying http connection is closed #25387
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 PR fixes the handling of upgraded socket from
node:http
module.In
op_node_http_fetch_response_upgrade
, we create DuplexStream paired withhyper::upgrade::Upgraded
. When the connection is closed from the server, the read result fromUpgraded
becomes 0. However because we don't close the paired DuplexStream at that point, the Socket object in JS side keeps alive even after the server closed. That caused the issue #20179This change fixes it by closing the paired DuplexStream when the
Upgraded
stream returns 0 read result.closes #20179