diff options
| author | Craig Tiller <ctiller@google.com> | 2023-10-19 07:54:42 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-10-19 07:54:42 -0700 |
| commit | f832772d89cf98ca5ea90b1002de871109d5a2be (patch) | |
| tree | 3f4d47545c05cdda49738276d64fa63c20d4d0d8 /bazel | |
| parent | 002b4014305c642fbb08f3ad39632e7eb1b604c4 (diff) | |
| download | grpc-grpc-f832772d89cf98ca5ea90b1002de871109d5a2be.tar.gz | |
[chttp2] Fix behavior on max concurrent streams exceeded (#34654)
Noticed that our behavior conflicts with what's mandated:
https://www.rfc-editor.org/rfc/rfc9113.html#section-5.1.2
So here's a quick fix - I like it because it's not a disconnection,
which always feels like one outage avoided.
---------
Co-authored-by: ctiller <ctiller@users.noreply.github.com>
Diffstat (limited to 'bazel')
| -rw-r--r-- | bazel/experiments.bzl | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/bazel/experiments.bzl b/bazel/experiments.bzl index eba454dda8..4fd34c5038 100644 --- a/bazel/experiments.bzl +++ b/bazel/experiments.bzl @@ -21,6 +21,9 @@ EXPERIMENTS = { "dbg": { }, "off": { + "bad_client_test": [ + "rfc_max_concurrent_streams", + ], "core_end2end_test": [ "event_engine_listener", "promise_based_client_call", @@ -105,6 +108,9 @@ EXPERIMENTS = { "dbg": { }, "off": { + "bad_client_test": [ + "rfc_max_concurrent_streams", + ], "core_end2end_test": [ "event_engine_listener", "promise_based_client_call", @@ -189,6 +195,9 @@ EXPERIMENTS = { "dbg": { }, "off": { + "bad_client_test": [ + "rfc_max_concurrent_streams", + ], "cancel_ares_query_test": [ "event_engine_dns", ], |