-
Notifications
You must be signed in to change notification settings - Fork 78
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
Deployment fails if the branchname contains special characters #185
Comments
I am also experiencing this with branch name
|
The core error message is I've addressed the subsequent [but unrelated] circular structure |
I run into a similar issue now with my account. The main branch is ⊂(◉‿◉)つ and it worked fine for about 6 months but all of a sudden I can't modify anything on the pages website without it failing. I get an error that says |
Same here, GHES 3.9.1 |
I figured it out with a rep from github support. I got rid of all the special characters (in the branch names and also in the names of the files) and the error resolved. |
thanks @saisonxiang! I'm not able to find any special chars, though. Did you use any commands or tools to find them? could they be also part of the contents of the files, or just file names and branches? |
I was foolish and named everything with emoji. If you didn't specifically name a branch or a file with an abnormal character they wouldn't be hiding in your files. Just make sure your files and branches have all alphabetical/numerical names and you should have dodged that problem set. You may have another issue. |
I'm seeing this issue on GHE 3.8, but I have no unusual branch names or filenames that I know of. Is there anyway I can see the response coming from the github api that is malformed? That might give me insight into what is wrong. |
I updated src/index.js to output the "error.response" and it's |
My company ran into other issues as well after upgrading to 3.9.1, so I'm guessing in my case it's related to that |
We started seeing this issue about a week ago without any upgrades or changes. GHES 3.8.9. |
I think my issue #236 is may be due to the branch name being |
en attendant la correction de actions/deploy-pages#236 et actions/deploy-pages#185 car actions/deploy-pages ne supporte que les noms de branche contenant uniquement des caractères ASCII
Just for assurance: we've filed an internal bug to investigate this one further. In the meanwhile, please try to avoid branch names with non-ASCII characters as a temporary workaround. Thank you for the report and patience! 🙇 |
I am also getting The deployment was working fine for a couple of months. However yesterday I was mucking about in the repository settings and switched "Source" under "Build and deployment" to "Deploy from a branch" and then back to "GitHub Actions". ![]() After this deployment started failing with:
Failed job output: https://github.com/2m/rallyeye/actions/runs/6983378084/job/19014225515 I tried switching "Source" a couple of times again, but the error persists. |
For Everyone's Information - I double the RAM and increased CPU cores on the appliance VMs during downtime and this issue stopped happening. |
Can you confirm whether this workaround addresses the issue even when the branch name has non-ASCII characters in it, such as |
I/we experience the issue on GHES as well … not sure I like the idea of throwing resources at the problem (not that I could) or that a reboot fixes it (I can't do anything about that either) because who is to say it wouldn't happen again 2 days later? A proper investigation or document on how to debug the issue and find the individual root cause and get that fixed would be much more helpful to me. |
Steps to reproduce:
büg
)The action fails with a similar error message given in #158, without indication about the source of the problem:
The text was updated successfully, but these errors were encountered: