Skip to content
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

http2: send RST code 8 on AbortController signal #48573

Merged
merged 1 commit into from Jul 6, 2023

Conversation

devm33
Copy link
Contributor

@devm33 devm33 commented Jun 27, 2023

Fixes: #47321

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/http2
  • @nodejs/net

@devm33
Copy link
Contributor Author

devm33 commented Jun 27, 2023

@anonrig Updated commit message!

@RafaelGSS RafaelGSS added the request-ci Add this label to start a Jenkins CI on a PR. label Jun 27, 2023
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jun 27, 2023
@nodejs-github-bot
Copy link
Collaborator

Copy link
Member

@RafaelGSS RafaelGSS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with green CI

@devm33
Copy link
Contributor Author

devm33 commented Jun 28, 2023

Thanks @RafaelGSS! It looks to me that the failing tests are unrelated. Is it possible they are flakes and if so can they be rerun?

@nodejs-github-bot
Copy link
Collaborator

@devm33
Copy link
Contributor Author

devm33 commented Jun 28, 2023

Thanks @RafaelGSS! It looks to me that the failing tests are unrelated. Is it possible they are flakes and if so can they be rerun?

Looks like a different test flake this time 🙃 Let me know if there are any tips for getting the CI green!

@RafaelGSS
Copy link
Member

Thanks @RafaelGSS! It looks to me that the failing tests are unrelated. Is it possible they are flakes and if so can they be rerun?

Looks like a different test flake this time upside_down_face Let me know if there are any tips for getting the CI green!

For now, we can Just retry

@nodejs-github-bot
Copy link
Collaborator

@devm33
Copy link
Contributor Author

devm33 commented Jun 28, 2023

For now, we can Just retry

Gotcha, in that case thank you @RafaelGSS for retrying! 🔁

@nodejs-github-bot
Copy link
Collaborator

@devm33
Copy link
Contributor Author

devm33 commented Jul 1, 2023

For now, we can Just retry

Gotcha, in that case thank you @RafaelGSS for retrying! 🔁

Thanks for continuing to rerun @RafaelGSS! Exciting to see it all green 🟢!

@RafaelGSS RafaelGSS added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Jul 2, 2023
@RafaelGSS RafaelGSS added the commit-queue Add this label to land a pull request using GitHub Actions. label Jul 6, 2023
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Jul 6, 2023
@nodejs-github-bot nodejs-github-bot merged commit b5e16ad into nodejs:main Jul 6, 2023
58 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in b5e16ad

@richardlau richardlau added the lts-watch-v18.x PRs that may need to be released in v18.x. label Jul 6, 2023
@devm33 devm33 deleted the devm33/http2-abort branch July 7, 2023 14:40
@devm33
Copy link
Contributor Author

devm33 commented Jul 7, 2023

Hi @richardlau do I need to do anything to backport this to v18? It looks like it merges cleanly onto the v18.x-staging branch.

Also could this be considered for v16? It looks like the commit applies cleanly to the v16.x-staging branch as well.

@RafaelGSS
Copy link
Member

v16.x is under maintainer mode. We don't perform regular releases.

If this land cleanly on v18.x, it should be included in the next release (v18.18.0).

@richardlau
Copy link
Member

@devm33 This would normally need to go out in a Node.js current release (i.e. 20.x) first before it would be eligible for inclusion in an LTS release.

It would not normally be considered for Node.js 16 now that is in maintenance.

@devm33
Copy link
Contributor Author

devm33 commented Jul 7, 2023

Thanks @RafaelGSS and @richardlau! That makes sense. Would be nice to consider as a bug fix for 16, but definitely understand if it doesn't make it in.

juanarbol pushed a commit that referenced this pull request Jul 13, 2023
Fixes: #47321
Refs: https://www.rfc-editor.org/rfc/rfc7540#section-7
PR-URL: #48573
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Minwoo Jung <nodecorelab@gmail.com>
@juanarbol juanarbol mentioned this pull request Jul 13, 2023
Ceres6 pushed a commit to Ceres6/node that referenced this pull request Aug 14, 2023
Fixes: nodejs#47321
Refs: https://www.rfc-editor.org/rfc/rfc7540#section-7
PR-URL: nodejs#48573
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Minwoo Jung <nodecorelab@gmail.com>
Ceres6 pushed a commit to Ceres6/node that referenced this pull request Aug 14, 2023
Fixes: nodejs#47321
Refs: https://www.rfc-editor.org/rfc/rfc7540#section-7
PR-URL: nodejs#48573
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Minwoo Jung <nodecorelab@gmail.com>
ruyadorno pushed a commit that referenced this pull request Sep 11, 2023
Fixes: #47321
Refs: https://www.rfc-editor.org/rfc/rfc7540#section-7
PR-URL: #48573
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Minwoo Jung <nodecorelab@gmail.com>
@ruyadorno ruyadorno mentioned this pull request Sep 11, 2023
ruyadorno pushed a commit that referenced this pull request Sep 13, 2023
Fixes: #47321
Refs: https://www.rfc-editor.org/rfc/rfc7540#section-7
PR-URL: #48573
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Minwoo Jung <nodecorelab@gmail.com>
ruyadorno pushed a commit that referenced this pull request Sep 17, 2023
Fixes: #47321
Refs: https://www.rfc-editor.org/rfc/rfc7540#section-7
PR-URL: #48573
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Minwoo Jung <nodecorelab@gmail.com>
@targos targos added backported-to-v18.x PRs backported to the v18.x-staging branch. and removed lts-watch-v18.x PRs that may need to be released in v18.x. labels Oct 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. backported-to-v18.x PRs backported to the v18.x-staging branch. http2 Issues or PRs related to the http2 subsystem. needs-ci PRs that need a full CI run.
Projects
None yet
7 participants