![]() ![]() I'm not sure it's worth trying to bodge a fix in Supervisor - perhaps just a better error message will do, such as something like "Unable to write Unicode to stdout with encoding what's the value of in the environment where your failure occurs, for the supervisorctl process which fails? The end-to-end test fails on 3.5 and 3.6 with LANG=oops, but succeeds on 3.7 because the encoding is set to utf-8 rather than ANSI_X3.4-1968, even for LANG=oops. On 3.x, you can't write bytes to sys.stdout. So, my "fix" works on 2.7 by catching the UnicodeEncodeError and just dumping bytes to sys.stdout - not the right thing to do, but 2.7 copes somehow (though it could conceivably still fail for other values of LANG). Shows the following for various versions on Python on my system: Is there a workaround of some sort with environment variables to allow python to understand UTF-8? I'm guessing it has issues with ellipsis and the μ character in my other units. => Press Ctrl-C to exit ('ascii' codec can't encode character u'…' in position 244: ordinal not in range(128)) INFO Imported new block headers count=192 elapsed=64.584ms number=147264 hash=e4d9f1…1bb15a age=3y8mo1w INFO Imported new block receipts count=194 elapsed=7.549ms number=146883 hash=9bed0e…30f78b age=3y8mo1w size=54.38kB INFO Imported new block headers count=192 elapsed=46.491ms number=147072 hash=dfdb9d…e8ee91 age=3y8mo1w INFO Imported new block receipts count=186 elapsed=9.575ms number=146689 hash=fc206b…7a87dd age=3y8mo1w size=85.38kB ![]() INFO Imported new block headers count=192 elapsed=46.846ms number=146880 hash=b1b46d…713aea age=3y8mo1w INFO Imported new state entries count=1152 elapsed=7.838ms processed=269879 pending=14675 retry=0 duplicate=0 unexpected=0 ![]()
0 Comments
Leave a Reply. |