-
Notifications
You must be signed in to change notification settings - Fork 235
Catch pooled connection errors in Connection.Manager process #2804
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
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found.
Additional details and impacted files@@ Coverage Diff @@
## main #2804 +/- ##
==========================================
- Coverage 78.32% 78.27% -0.05%
==========================================
Files 154 154
Lines 7270 7288 +18
Branches 275 273 -2
==========================================
+ Hits 5694 5705 +11
- Misses 1574 1581 +7
Partials 2 2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
3ffca87
to
d971d3c
Compare
Avoid logging "unknown error" for some of the well-known errors that are easy to reproduce.
d971d3c
to
b66b36f
Compare
state | ||
) | ||
|
||
# If the error is of an unknown type, it would have already been logged by DbConnectionError itself. |
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.
We've been chatting back and forth about disabling library logging. I think with this PR and catching all the unknown errors from the lib we can disable it safely. Shall we do that as part of this PR? cc @robacourt
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.
Sounds like a good idea to me
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.
Sorry, I'm not sure I get what is meant by disabling library logging here.
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.
- Set
capture_log_messages
to false - Come up with an alternative means to send errors to Sentry when we want to (when we currently just log an error)
Because 2 is not trivial, perhaps it should be a separate PR.
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.
Nice work!
Fix #1554, #2727.