-
Notifications
You must be signed in to change notification settings - Fork 187
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
Source sequence is illegal/malformed utf-8 #284
Comments
I have the same issue. I'm using EC2 Windows machine. I suspect that the error is caused by some diacritics in the file names, but didn't confirm that yet. |
@kedde thanks. Checking this box solves the issue. |
We have the same issue when trying to deploy our server package. Multiple files in the package is containg dainsh chars and we are unable to rename these files. We are deploying to a Windows server 2016 instance. |
What is your operating system level locale setting? |
Hi Mike
The local of the target EC2 operating system is English(United States):
![image](https://user-images.githubusercontent.com/120450217/207794392-516edf85-add8-4dfc-af7b-e2ba7c64f048.png)
I tried changing it to Danish but it did not seem to help.
|
@MartinHeynAndersen we will work on reproducing this issue and get back to you. |
Hi everyone, So i ran into this issue recently. The reason for the issue was some spanish characters in the application code.
After updating those file names, it worked correctly. I did use the windows language settings UTF fix temporally until the underlying fix was applied.
|
Hello guys,
I'm getting the following error when I try to deploy to my EC2 Instances. I have others applications, with the same structure, that is working perfectly.
I got this on codedeploy-agent-log:
[Aws::CodeDeployCommand::Client 200 0.078138 0 retries] put_host_command_complete(command_status:"Failed",diagnostics:{format:"JSON",payload:"{"error_code":5,"script_name":"","message":"source sequence is illegal/malformed utf-8","log":""}"}
Someone knows what is happening?
The text was updated successfully, but these errors were encountered: