[adriangb]

Replaces #2969, combined here as suggested.

Motivation

When a client resets many streams, a server can still send DATA for them. h2 remembers only 50 reset streams for 1 s by default. DATA for a forgotten stream counts toward the local error reset limit (1024), and reaching it closes the connection with GOAWAY(ENHANCE_YOUR_CALM, "too_many_internal_resets"). Endpoint exposes none of these h2 client options today, so a caller must build the connection with hyper directly to change them.

Solution

• Add Endpoint::http2_max_concurrent_reset_streams(usize): how many reset streams h2 remembers.
• Add Endpoint::http2_reset_stream_duration(Duration): how long h2 remembers a reset stream.
• Add Endpoint::http2_max_local_error_reset_streams(impl Into<Option<usize>>), the client counterpart of the Server option, as in feat(transport): expose http2_max_local_error_reset_streams on Endpoint #2708 (closed). Unset keeps hyper's default of 1024, and None disables the limit.
• Raise tonic's hyper requirement from 1 to 1.10, the first release with the client reset_stream_duration option.

[LucioFranco]

@adriangb might make sense to just combine both your PRs into this one since they are just exposing h2 knobs that feels fine to me. Once you do that and this is ready for review give me a ping we should be able to get this out pretty easily.

[adriangb]

I think the main thing I need input in is the bump in the hyper version. The knobs this PR exposes are only available since 1.10. Wdyt of the feature flag approach so that users of grpc-rust can opt-into more hyper options / version bumps but we don't force everyone to bump their hyper versions just for options they may not need? FWIW 1.10 was release May 27th, 2026.

[LucioFranco]

I think the main thing I need input in is the bump in the hyper version. The knobs this PR exposes are only available since 1.10. Wdyt of the feature flag approach so that users of grpc-rust can opt-into more hyper options / version bumps but we don't force everyone to bump their hyper versions just for options they may not need? FWIW 1.10 was release May 27th, 2026.
bumping a version like this is totally fine and not a breaking change since users can upgrade without breaking their code, so not concerned about that portion at all.

[adriangb]

sounds good, will merge the prs tomorrow

[adriangb]

@LucioFranco consolidated into this PR, I closed #2969.

The main question I see left is testing: my agent added a good amount of tests, but I could see them being overkill if we are just passing through an option. But hard for me to asses the strategy here since I'm a new contributor. Wdyt?

[LucioFranco]

@adriangb Yeah I agree looks like we are testing the functionality of another crate rather than did the config get set so I would say we can thin the tests down for sure the code is pretty easy to review without it. Once you do that I think we can merge this, thanks!

[adriangb]

@LucioFranco Removed the integration tests; the PR is now just the three Endpoint options, their doc examples, and the hyper bump.

[adriangb]

@LucioFranco done, and did a pass on the docstrings as well

[LucioFranco]

Thanks!