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
Is sere is a reason why latin1 encoding is being used? When I use nosepipe from shell my shell is broken. o_O Though when I replaced latin1 with utf8 everything worked perfect. I guess whetehr it's possible to replaces latin1 encoding with utf8/asci or just use system-wide encoding?
The text was updated successfully, but these errors were encountered:
I'm guessing this is related to the stdout communication of nosepipe somehow. I would think if we replace that work socket communication we could just use the system configured encoding instead.
I see similar problems in nosepipe when database functions are used.
This are the details:
OS: Ubuntu 16.04
Mysql 5.7 server
webpy mysql client functions
dbutils database pool
Terminal is running in utf8 encoding already, the problem looks more related in this case probably to database data encoding/decoding.
Nosepipe error: python2.7/site-packages/nosepipe.py", line 179, in __call__ (header + data).decode("latin1")) Exception: short message body (want 808333344, got 17474) Something went wrong
Is sere is a reason why latin1 encoding is being used? When I use nosepipe from shell my shell is broken. o_O Though when I replaced latin1 with utf8 everything worked perfect. I guess whetehr it's possible to replaces latin1 encoding with utf8/asci or just use system-wide encoding?
The text was updated successfully, but these errors were encountered: