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.
3.11.3 (2024-12-13)
Fixed
AsyncSession
and attached overloads (AsyncResponse
orResponse
). (Incorrect typing on AsyncResponse.iter_content() #185)Changed
Removed
Previously, we hardcoded a limit of 128 * NUM_CONN_POOL maximum inflight (aka. unresolved/lazy) response.
This was unrealistic due to a number of factors like (but not limited to):
A) remote peers can choose at will the max streams.
B) we can have multiple pool with multiple (varying) max capacities.
C) retrieving max streams per pool per conn is a very costly procedure (in terms of performance).
We will revisit this later on. You still can set
max_in_flight_multiplexed
in yourHTTPAdapter
torestore this broken behavior.