-
Notifications
You must be signed in to change notification settings - Fork 264
Failed connection counter reset #385
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
Conversation
I tried the test with and without the code fix and the test fails as expected without the _connection_counter rollback. |
@taybin I think the |
@aminalaee I wanted to be sure it was that specific Exception that was being caught. |
@taybin I was thinking raising an exception like |
Avoid dangling task-local connections after Database.disconnect() (#211) Co-authored-by: Amin Alaee <mohammadamin.alaee@gmail.com> Reset counter for failed connections (#385) Co-authored-by: Sergey Morozov <sergey@morozov.top> Version 0.5.2 (#386) update requirements change scripts update pytest config update pytest Update requirements update workflow try cache in workflow disable coverage for py3.6 use cache in env fix workflow cache keys update coverage workflow test test again test use absoulte path
This adds a unittest for #283. It does require the library
asyncmock
as AsyncMock isn't available in python 3.6 or 3.7 yet. If testing on 3.6 and 3.6 is not a requirement, we can use unittest.mocks.AsyncMock since it's included in python 3.8.@aminalaee