You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If this log handler is attached to the root handler with loglevel DEBUG you will receive the log-messages from the request library and url3lib, again triggering new log messages from those library, resulting in an infinite loop of messages. I come over the same bug when I tried to write my own log-handler, and I have described the issue in more detail on stackoverflow.
You can set YourURL to "http://127.0.0.1:6000" and then use nc -k -l 6000 to see the connections flowing inn (you might need to press enter in the nc window to make it flush its output buffer).
The text was updated successfully, but these errors were encountered:
If this log handler is attached to the root handler with loglevel DEBUG you will receive the log-messages from the request library and url3lib, again triggering new log messages from those library, resulting in an infinite loop of messages. I come over the same bug when I tried to write my own log-handler, and I have described the issue in more detail on stackoverflow.
How to reproduce:
You can set YourURL to "http://127.0.0.1:6000" and then use
nc -k -l 6000
to see the connections flowing inn (you might need to press enter in the nc window to make it flush its output buffer).The text was updated successfully, but these errors were encountered: