-
-
Notifications
You must be signed in to change notification settings - Fork 183
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
UnicodeDecodeError has occurred on windows-latest #129
Comments
Thanks for raising this. Where in the event file is that emoji, in the commit message or the pull request description? Can you paste the character here (not the github markdown replacement that starts and ends with a colon). I want to reproduce this. Is your workflow running in an self-hosted environment or on GitHub-hosted runners? |
From what I can see from the GitHub runner code, it always writes that file in UTF8: |
The stacktrace reveals that it looks like the file is being read with codec |
Thank you for your reply.
And, my workflow is running on GitHub-hosted runners. |
On Windows runners, the default encoding for Python reading text files is Please try this on your branch that fails with above error:
|
Is your breaking workflow running on |
@EnricoMi Today, I tried execution workflow with various commit message. And It turns out that sometimes it works and sometimes it doesn't. Can you release this PR to main version ? My workflow running on push event.
And my event json is below.
|
I could reproduce the issue with a |
This has been released and is available under |
Hi.
I use this action for the output of e2e-test result.
And, I has error about UnicodeDecodeError at windows-latest environment.
The error occurred only at windows-latest, but not occurred at mac-latest.
My workflow definition is below .
And, error log is below.
I check GITHUB_EVENT_PATH, and I find that the text include emoji because of commit message.
Is emoji is cause of error?
I can't solve this problem by myself, so please give me some solution or something.
Thank you.
The text was updated successfully, but these errors were encountered: