-
-
Notifications
You must be signed in to change notification settings - Fork 402
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
irc: Improve output for common connection errors #2430
Conversation
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.
<+xrl> dgw: the draft is to see if you want more out of our error logs
I like this. I think it's more than sufficient to close #2111, and we can keep an eye out for more improvements that can be made to 8.1. Just a couple tweaks. 🙂
This method was used for the asynchat backend implementation. It is now deprecated and must not be used. Co-authored-by: dgw <dgw@technobabbl.es>
These error are now managed with a more user-friendly message, and the exception is sent to the exception log file: * SSL certificate validation error * SSL generic error * Connection timeout (socket timeout, not IRC timeout) * Invalid hostname * Unable to connect (temporary disconnected, host unreachable, etc.) If we inspect the OSError's errno we could provide a more fine-grained error handling. We could, also, improve the connection retry for certain errors.
02e07a4
to
b6c5e86
Compare
Alright, then it's ready for an actual true review. 😎 I expect some nitpicking on the wording and all that! 😁 |
Co-authored-by: James Gerity <snoop.jedi@gmail.com>
0900e79
to
1116918
Compare
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 just have nitpicks.
Co-authored-by: dgw <dgw@technobabbl.es>
Co-authored-by: dgw <dgw@technobabbl.es>
f174b65
to
c4a34f7
Compare
@dgw nitpick fixed. |
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 this is ready as it'll ever be from my perspective. Just curious if @SnoopJ considers that connection block in irc/backends.py
to be fine now; I saw he suggested abstracting a bunch of error handling into a method call, but it doesn't look like that was done before resolving the thread?
I did with a method |
@Exirel Ah, so you did. Got confused by the line anchoring that discussion thread being inside the new method, untouched. 😅 |
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 had a nit, but LGTM 👍
Given #2455, merging this is risking it for the biscuit a little, but I really want to start shipping stuff again. |
Description
Closes #2111 and open the way for better error handling and connection retry.
Checklist
make qa
(runsmake quality
andmake test
)