| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Would be nice to eventually consolidate stream, http1, http/2 compat and http/2 in terms of the streams API & behaviours. |
Sorry, something went wrong.
|
Unsure about semver. Maybe major? |
Sorry, something went wrong.
There was a problem hiding this comment.
I’m good with semver-patch
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
I don't think ERR_STREAM_DESTROYED belongs here. Also left some nits but that's the primary objection for me.
Would also like James to review ideally.
Sorry, something went wrong.
|
@apapirovski: I think you prefer to align with http1 instead of streams. I've updated the PR accordingly. |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
(It was mentioned in the linked issue, hence me bringing it up.)
Sorry, something went wrong.
There was a problem hiding this comment.
I'll leave this as is until there is more input.
Sorry, something went wrong.
There was a problem hiding this comment.
I think the biggest issue was the throw.
Sorry, something went wrong.
change request was addressed, will approve after outstanding discussion is resolved
Sorry, something went wrong.
Sorry, something went wrong.
|
I believe this is author-ready? |
Sorry, something went wrong.
|
Needs a rebase. |
Sorry, something went wrong.
HTTP2ServerResponse.write would behave differently than both http1 and streams. This PR makes it more compliant with stream.Writable behaviour. Refs: nodejs#29529
|
rebased |
Sorry, something went wrong.
Sorry, something went wrong.
|
This needs a backport or other previous PRs to be backported in order to land on v12.x-staging. |
Sorry, something went wrong.
HTTP2ServerResponse.write would behave differently than both http1 and streams. This PR makes it more compliant with stream.Writable behaviour. PR-URL: nodejs#30964 Refs: nodejs#29529
HTTP2ServerResponse.write would behave differently than both http1 and streams. This PR makes it more compliant with stream.Writable behaviour. PR-URL: nodejs#30964 Refs: nodejs#29529 Backport-PR-URL: nodejs#31444
This issue is still present on 12.20.0. I think the backported-to-v12.x tag might be misapplied here, or the fix was not sufficient. `` |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
HTTP2ServerResponse.write would behave differently than both http1 and streams. This PR makes it more compliant with stream.Writable behaviour.
In particular, prior to this PR, write would throw err instead of calling destroy(err)
Refs: #29529
Checklist