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

Handle implicit resets at the right time #833

Merged
merged 1 commit into from
Jan 24, 2025
Merged

Conversation

nox
Copy link
Contributor

@nox nox commented Jan 20, 2025

A stream whose ref count reaches zero while open should not immediately decrease the number of active streams, otherwise MAX_CONCURRENT_STREAMS isn't respected anymore.

@nox nox force-pushed the fix-implicit-reset branch 2 times, most recently from dffce7f to 38ebb1b Compare January 20, 2025 14:12
@nox nox force-pushed the fix-implicit-reset branch 3 times, most recently from 7420a99 to 9b85baf Compare January 24, 2025 07:14
@nox
Copy link
Contributor Author

nox commented Jan 24, 2025

I simplified the change a lot by just gating the dec_num_streams call in transition_after with !stream.state.is_scheduled_reset().

A stream whose ref count reaches zero while open should
not immediately decrease the number of active streams,
otherwise MAX_CONCURRENT_STREAMS isn't respected anymore.
@nox nox force-pushed the fix-implicit-reset branch from 9b85baf to b9b0c91 Compare January 24, 2025 11:52
@seanmonstar seanmonstar merged commit 02eb53b into master Jan 24, 2025
6 checks passed
@seanmonstar seanmonstar deleted the fix-implicit-reset branch January 24, 2025 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants