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

Release 3.11.3 #188

Merged
merged 9 commits into from
Dec 13, 2024
Merged

Release 3.11.3 #188

merged 9 commits into from
Dec 13, 2024

Conversation

Ousret
Copy link
Member

@Ousret Ousret commented Dec 13, 2024

3.11.3 (2024-12-13)

Fixed

Changed

  • Default keepalive (HTTP/2, and HTTP/3) changed to 1 hour. In conformance with urllib3-future.

Removed

  • Automatic resolution of pending lazy responses if there are too many of them.
    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 your HTTPAdapter to
    restore this broken behavior.

@Ousret Ousret merged commit 6bf7791 into main Dec 13, 2024
34 checks passed
@Ousret Ousret deleted the release-3.11.3 branch December 13, 2024 07:18
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.

1 participant