chore(server/conn): backport max_pending_accept_reset_streams()
#3796
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NB: this commit is based on the
0.14.x
release series.the
server::conn::http2
submodule provides types that are conditionally compiled when thebackports
feature is active, to facilitate upgrading to the1.x
release.i've been working on upgrading the
linkerd2-proxy
project to use hyper 1.0, but encountered a pertinent gap inBuilder<E>
's interface when setting thebackports
anddeprecated
features.this adds a
max_pending_accept_reset_streams(..)
method (added in #3201) to this builder, so that 0.14.x users relying on this functionality can prepare to upgrade to hyper 1.x safely.this is effectively a backport of #3507, which restored this interface to the 1.0 release.
for more information, see:
max_pending_accept_reset_streams
#3461