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

Fix reclaiming reserved capacity (fixes #607) #832

Merged
merged 1 commit into from
Jan 20, 2025

Conversation

nox
Copy link
Contributor

@nox nox commented Jan 20, 2025

Reclaiming requested capacity that has not been actually reserved yet is wrong, as this capacity never existed to begin with.

@nox
Copy link
Contributor Author

nox commented Jan 20, 2025

I'm wondering if scheduled resets should just be removed and send_reset be tweaked to not clear the send queue when called implicitly.

Reclaiming requested capacity that has not been actually reserved yet
is wrong, as this capacity never existed to begin with.
@nox nox force-pushed the fix-reclaim-reserved-capacity branch from 5017247 to 296f4c5 Compare January 20, 2025 14:57
@nox
Copy link
Contributor Author

nox commented Jan 20, 2025

I'm wondering if scheduled resets should just be removed and send_reset be tweaked to not clear the send queue when called implicitly.

I tried that, but you need the send buffer to queue a reset frame, and you can't reach the send buffer from drop_stream_ref.

@seanmonstar seanmonstar merged commit b109803 into master Jan 20, 2025
6 checks passed
@seanmonstar seanmonstar deleted the fix-reclaim-reserved-capacity branch January 20, 2025 15:35
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