http: abortIncoming only on socket close#36821
Conversation
5f9df3b to
55c02b6
Compare
Don't call abortIncombin twice for same socket, i.e. both during 'end' and 'close'.
|
@nodejs/http |
dnlup
left a comment
There was a problem hiding this comment.
close will always be emitted even if end is emitted, I agree.
|
|
After reading #36868, I think it should be safe to land this even if that test fails. If there are no objections, I will proceed with landing this tomorrow. If I understand correctly from here, one collaborator approval should be enough if the PR has been open for more than days and has no objections. |
|
We need two approval for landing though? |
The linked section of the docs says that if a PR is open for more than 7 days, then one approval is enough. But I can't say I have seen PR merged with one approval though. On second thought, let's wait for a second approval. Keeping this open might also help to debug the failing test, I think. |
Ah, that's news for me. Thanks for the heads up. |
|
Landed in 708728d |
Don't call abortIncombin twice for same socket, i.e. both during 'end' and 'close'. PR-URL: #36821 Reviewed-By: James M Snell <jasnell@gmail.com>
Don't call abortIncombin twice for same socket, i.e. both during 'end' and 'close'. PR-URL: #36821 Reviewed-By: James M Snell <jasnell@gmail.com>
Don't call abortIncombin twice for same socket, i.e. both during 'end' and 'close'. PR-URL: #36821 Reviewed-By: James M Snell <jasnell@gmail.com>
Don't call abortIncoming twice for same socket, i.e. both during 'end' and 'close'. Also does some minor cleanup.