-
Notifications
You must be signed in to change notification settings - Fork 191
Unicode issues with output to stdout #142
Comments
How you install it? |
I installed it via the vendor and epel repositories |
I'm not very experienced with CentOS, it would be nice if you give me the exact instructions :) Thanks. |
@ruslo if you have a centos7 vm or container running...
The above should give you an environment to run cmake and gcc/g++, I have a bunch of other dependencies that I have which I wont paste into above as its not relevant. Hope the above helps. |
It works fine for me.
Working directory with Russian characters:
Seems that stdout encoding is UTF8:
|
Just for your info I still can't find the way to change the keyboard layout to another language :) I have to copy/paste string from another machine. Any hints welcome. |
May be copy and paste from here?
Or else I can gist it at https://gist.github.com/jcftang/89792312f73309c91116554b6b8e3bce |
Same test, works fine:
Try to run this from console:
|
@ruslo the problem exhibits itself when I run the scripts inside a centos7 docker container,...
|
What about
? |
Doing that gives me an empty value
the whole env just has this...
|
Can you try |
setting the LC_ALL environment variable does not help at all
|
I'm running out of ideas. Let's try I'm still not able to reproduce the error, can you share your docker image? E.g. by https://quay.io/ service. |
@ruslo the branch https://github.com/ruslo/polly/tree/pr.encoding appears to have addressed the hanging, my builds at least succeed. I think its probably safe to merge that PR |
It's merged to |
I tend to agree this bug is a bit obscure and hard to reproduce. I can't share my container that I am using to reproduce this. I will see if I can create a test case for you to reproduce if time permits. |
This relates to
#141
After that the above patch, output to stdout still causes an issue with hanging...
The above was generated from a build that was executed inside a docker container using python 3.4 on centos7. It looks like the encoding in my container is always set to
ANSI_X3.4-1968
The text was updated successfully, but these errors were encountered: