-
Notifications
You must be signed in to change notification settings - Fork 142
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
Track checked out created connections across reloads #192
Track checked out created connections across reloads #192
Conversation
…at the connection pool size The TimedStack class currently allows
91b737c
to
778310d
Compare
It seems unit tests are failing due to an issue in There is a fix in the works: minitest/minitest#1010 |
Why did ruby 2.5 pass‽‽ |
The other fix is to put a |
I don’t particularly care for the decrement created method. Could you in-line that please? |
@ttstarck Would you be interested in commit bit here? |
@mperham I am not sure what you mean by "commit bit", (google shows me https://github.com/cucumber/commitbit). I'd be happy to be elevated to a higher level of permissions. |
It means you have commit rights to this repo. Everyone still works on PRs for major things but minor things like updating the changelog can be done directly. |
There appears to be a small bug around
ConnectionPool#reload
where it is possible to create more connections than the size of the pool if you runreload
while a connection is checked out.See the test cases defined in 4f4e5f6
These test cases all fail on the master branch. This is due to how
@created
instance variable inConnectionPool::TimedStack
is decremented, where currently it is set to 0 on#shutdown(reload: true)
even if no connections were "shutdown" on the reload.