-
Notifications
You must be signed in to change notification settings - Fork 49
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
[all] 501 Numeric is unrecognized by pydle. #58
Comments
I've been thinking about how to work with stuff like that for a while. They probably shouldn't be swallowed entirely as they are server error messages that can be useful in diagnosing bot behaviour. I'm considering adding a simple warning wrapper ( |
That could work fairly well, although another possible solution/debugging tool could be having an option to dump raw io to stdout/a log file. I currently am using a small wrapper around Client to do that on my debug bot. |
What we currently do there is that you can set set the |
Ah, good to know that is a thing that exists. |
Pydle complains about a 501 numeric response (meaning unknown mode) being unknown, it should probably be ignored.
The text was updated successfully, but these errors were encountered: