Closed igel-kun closed 8 years ago
The DCCConnection uses a LineBuffer that shouldn't be decoding anything... it seems like something is being sent over the primary ServerConnection that's not UTF-8. Perhaps that's the byte count being sent in binary?
it appears you're right, the peer isn't speaking proper UTF-8; the message that crashes the script is some status notice from the peer. As I care little about this status, I just set the decoding to "replace" instead of "strict" behavior on error and that keeps it from crashing. Ah it also seems that my version (debian jessie default) is a bit outdated, as it seems that the current version uses a separate buffer implementation. Hmm OK.
hi, I frequently encounter the following error when performing DCC transactions:
I am wondering if maybe the DCC transfer should not be interpreted as UTF8, but binary data?