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
Revert "src: let http2 streams end after session close" #46249
base: main
Are you sure you want to change the base?
Conversation
This reverts commit dee882e. Moved the test that demonstrated what this commit was fixing to the `known_issues` folder. Fixes: nodejs#46234
|
Review requested:
|
|
Once this is merged, should we reopen #42713? |
|
Would be nice with a regression test if possible. |
I moved the original test to the known_issues folder. Is that what you're asking? |
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.
lgtm
|
@nodejs/releasers this should be backported to v19.x, v18.x, and v16.x. |
|
Fast-track has been requested by @RafaelGSS. Please |
|
I requested the fast-track to include it in the next v19.x release (planning to create the proposal between Thursday and Friday). |
|
The tests keep failing. |
|
The test failure looks weird. Skipped due to missing crypto but still fail? How is that possible? https://ci.nodejs.org/job/node-test-commit-linux-containered/nodes=ubuntu1804_sharedlibs_withoutssl_x64/35560/testReport/junit/(root)/test/known_issues_test_http2_trailers_after_session_close/ @Trott |

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

This reverts commit dee882e. Moved the test that demonstrated what this commit was fixing to the
known_issuesfolder.Fixes: #46234