New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accented characters produce a UnicodeDecodeError when executing a playbook (ansible 1.5.3) #6655
Comments
astorije
changed the title
Accented characters produce a
Accented characters produce a UnicodeDecodeError when executing a playbook (ansible 1.5.3)
Mar 24, 2014
UnicodeDecodeError
when executing a playbook (ansible 1.5.3)
@astorije this should be fixed in devel now. Please let me know otherwise. |
@jctanner Thanks a lot for the quick answer! I am using distribution packages (Ubuntu), do you know when it will be available there? |
I just had the same crash, culprit was coloured output on
|
benpatterson
pushed a commit
to openedx/configuration
that referenced
this issue
Aug 25, 2014
…rver. The test_build_server role was failing on acceptance tests because of unicode static assets being gathered in collectstatic for django. This was because of this issue ansible/ansible#6655, which has been resolved in recent ansible versions. We must override the version that is being used by this repo, and upgrade ansible at provisioning time for running the test_build_server role.
this is still happening with template files that have spanish characters |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Type:
Bug Report
Ansible Version:
Environment:
Summary:
Accented characters produce a
UnicodeDecodeError
when executing a playbook.Steps To Reproduce:
I was trying to run the following task in the only play of my playbook:
Expected Results:
The playbook should run with no error and adds the corresponding line in the
.gitconfig
file.If I replace the
é
by standarde
s, the playbook is executed as expected and the.gitconfig
file is properly updated.Actual Results:
The text was updated successfully, but these errors were encountered: