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

net/http, x/net/http2: http server shutdown doesn't gracefully shut down HTTP2 connections [1.13 backport] #40085

Closed
gopherbot opened this issue Jul 7, 2020 · 2 comments
Labels
CherryPickCandidate Used during the release process for point releases FrozenDueToAge
Milestone

Comments

@gopherbot
Copy link

@networkimprov requested issue #39776 to be considered for backport to the next 1.13 minor release.

@gopherbot please backport to 1.13 & 1.14. Per @fraenkel this does not behave as documented and there is no workaround.

@gopherbot gopherbot added the CherryPickCandidate Used during the release process for point releases label Jul 7, 2020
@gopherbot gopherbot added this to the Go1.13.13 milestone Jul 7, 2020
@andybons andybons modified the milestones: Go1.13.13, Go1.13.14, Go1.13.15 Jul 14, 2020
@toothrot toothrot modified the milestones: Go1.13.15, Go1.13.16 Aug 6, 2020
@networkimprov
Copy link

Some sites are not able to upgrade to 1.14 or 1.15 because async preemption breaks them (#40722 recently), and there's no way to disable it at build-time -- only the env variable at runtime.

@ianlancetaylor
Copy link
Contributor

The Go project has a pretty clearly specified rule: we support two releases at a time. Of course anybody else is free to maintain patches for older releases. It's just not a burden we can take on ourselves.

@golang golang locked and limited conversation to collaborators Aug 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
CherryPickCandidate Used during the release process for point releases FrozenDueToAge
Projects
None yet
Development

No branches or pull requests

6 participants