fix: do not assign capacity for pending streams #860
+145
−25
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.
Prioritize::send_data
has a check to prevent assigning capacity to streams that are not yet open. Assigning flow control window to pending streams could starve already open streams.This change moves the
stream.is_pending_open
check intoPrioritize::try_assign_capacity
. This prevents capacity from ever being assigned to pending streams. In particular, neither a client'sreserve_capacity
call nor a remote's initial window size adjustment will assign capacity to pending streams.Tests
capacity_not_assigned_to_unopened_streams
andnew_initial_window_size_capacity_not_assigned_to_unopened_streams
inflow_control.rs
demonstrates the fix.A number of other tests must be changed because they were assuming that pending streams immediately received connection capacity.
This may be related to #853.