Skip to content

Conversation

@blazewicz
Copy link
Contributor

@blazewicz blazewicz commented Mar 26, 2025

Summary

This commit fixes a bug in both sync and async connection pools where idle connections were dropped from the pool even when max_keepalive_connections limit has not been reached. This happened because the check compared this setting's value to the total number of connections, not only of the idle ones.

Checklist

  • I understand that this PR may be closed in case there was no previous discussion. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
@blazewicz blazewicz force-pushed the blazewicz/fix-max-keepalive-connections branch 2 times, most recently from 0aa2ee1 to 6414fd8 Compare March 29, 2025 18:12
Copy link
Contributor

@zanieb zanieb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does seem like a fairly straightforward oversight in the implementation.

This commit fixes a bug in both sync and async connection pools
where idle connections were dropped from the pool even when
max_keepalive_connections limit has not been reached. This
happened because the check compared this number to the total
number of connections, not only the idle ones.
@blazewicz blazewicz force-pushed the blazewicz/fix-max-keepalive-connections branch from 6414fd8 to 7fb2052 Compare September 23, 2025 09:31
@lovelydinosaur
Copy link
Contributor

Ah yeah apologies... this is a nice simple fix, and worth getting in.

@lovelydinosaur lovelydinosaur merged commit 10a6582 into encode:master Oct 13, 2025
7 checks passed
@springmeyer
Copy link

springmeyer commented Nov 6, 2025

Will this be released soon in a formal release? Perhaps a 1.0.10?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

5 participants