mirror of
https://github.com/nodejs/node.git
synced 2024-11-24 03:07:54 +01:00
93c4efeb25
A detailed analysis of the cause of this bug is in my linked comment on the corresponding issue. The primary fix is the new setImmediate call in Http2Stream#_destroy, which prevents a re-entrant call into Http2Session::SendPendingData when sending trailers after the Http2Session has been shut down, allowing the trailer data to be flushed properly before the socket is closed. As a result of this change, writes can be initiated later in the lifetime of the Http2Session. So, when a JSStreamSocket is used as the underlying socket reference for an Http2Session, it needs to be able to accept write calls after it is closed. In addition, now that outgoing data can be flushed differently after a session is closed, in two tests clients receive errors that they previously did not receive. I believe the new errors are more correct, so I changed the tests to match. Fixes: https://github.com/nodejs/node/issues/42713 Refs: https://github.com/nodejs/node/issues/42713#issuecomment-1756140062 PR-URL: https://github.com/nodejs/node/pull/50202 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com> |
||
|---|---|---|
| .. | ||
| known_issues.status | ||
| test-cli-print-var-crypto.js | ||
| test-cwd-enoent-file.js | ||
| test-dgram-bind-shared-ports-after-port-0.js | ||
| test-fs-writeFileSync-invalid-windows.js | ||
| test-http-path-contains-unicode.js | ||
| test-inspector-cluster-port-clash.js | ||
| test-permission-model-path-resolution.js | ||
| test-repl-require-context.js | ||
| test-stdin-is-always-net.socket.js | ||
| test-stream-writable-sync-error.js | ||
| test-url-parse-conformance.js | ||
| test-vm-function-declaration-uses-define.js | ||
| test-vm-ownkeys.js | ||
| test-vm-ownpropertynames.js | ||
| test-vm-ownpropertysymbols.js | ||
| test-vm-timeout-escape-nexttick.js | ||
| test-vm-timeout-escape-queuemicrotask.js | ||
| testcfg.py | ||