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
This is a problem when the file contains bytes that form invalid utf-8 sequences, as it goes to an interactive prompt asking the user what encoding to use. It could just default to encoding the file/buffer as raw-text to begin with, or it could run the binary data through some kind of encoding first. For now I'm just turning off the logging by setting elnode--do-error-logging to nil.
One thing: the latest Elnode (0.9.9) does not log send-strings by default. So you could check you're using that. I'm not even sure logging send-strings ever is a good idea, I did it for debugging.
This is a problem when the file contains bytes that form invalid utf-8 sequences, as it goes to an interactive prompt asking the user what encoding to use. It could just default to encoding the file/buffer as raw-text to begin with, or it could run the binary data through some kind of encoding first. For now I'm just turning off the logging by setting elnode--do-error-logging to nil.
Example:
20120813101139: elnode-http-send-string elnode-webserver-proc 10.0.38.28:14778 [[GIF87aT^@t^@\366^?^@\377\377\377^@^X\214\354]]
The text was updated successfully, but these errors were encountered: