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
Made Parsec able to retry first db connection, cleaner docker-compose #1258
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1258 +/- ##
===========================================
+ Coverage 56.97% 75.15% +18.18%
===========================================
Files 298 298
Lines 26291 26324 +33
===========================================
+ Hits 14979 19785 +4806
+ Misses 11312 6539 -4773
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we could add a test on this pretty easily: just start the backend with a localhost:<dummy_port> (using unused_tcp_port
fixture) as postgresql configuration, then check the number of warnings we endup with thanks to recwarn
fixture (see https://docs.pytest.org/en/stable/warnings.html#recwarn)
No description provided.