Initial commit failed with Error: Process completed with exit code 128. #70
Comments
|
Hi @tanjuntao, thanks for taking the time to open this issue! I have not seen this before, and do not have an answer off the top of my head. What is interesting is that I don't believe the final commit step actually uses your personal access token, so I don't think permissions for that are an issue. Have you tried re-running the action (or waiting until its next automatic run)? I'm curious if this is a fluke, or something that keeps happening. |
|
I am having the same issue here and re-running workflow doesn't work - will wait for the next automatic run to see if it still happens. |
|
Yes, I did re-run the action several times and each time I failed at the git commit step and got the same error message. |
|
I just started trying to use this as a new user. I see the same errors happening on my end as well ;(. |
|
Hi all, thanks for chiming in! I figured out what the problem is. It seems like GitHub changed the default permissions of the In other words, this is fixed in the latest version of the repo. But for you in this thread who already have a stale copy, there are two ways to fix this, and you can pick either one:
Thanks again for reporting this issue! I would never have known about it otherwise, and now it's fixed for everyone 😁 |
|
The problem is solved but I got another issue same as #21 and #35 using the manual run afterward. |
|
I got exactly the same problem as you, I solved it by just deleting my old github-stats repo and generated a new one from scratch, this worked for me. 🤣 |
|
Hmm. For me, the auto update of generating the file again failed.... with the same error as before, even though I repulled the updated template. |
|
I tried totally deleting the repo and reconfiguring it again - solve the problem as of now for me. |
|
@briancpark Did you still fail at the initial commit step after re-generating an updated repo? If your problem is same as #30, you can just wait for some minutes and run the failed job again and it will work. |
|
No, I successfully generated after re-generating an updated repo. That initial run took under 5 minutes. I changed a few env variables and I waited over an hour, but it's still hanging on the next runs after that ;( |
|
Have no idea about that. From the env:
ACCESS_TOKEN: ${{ secrets.ACCESS_TOKEN }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
EXCLUDED: ${{ secrets.EXCLUDED }}
EXCLUDED_LANGS: ${{ secrets.EXCLUDED_LANGS }}
EXCLUDE_FORKED_REPOS: trueMaybe you could check the names and values of your env variables first, and if there are no problems, then just wait for the author to give a suggestion. *Note: the values of env variables should be separated by a comma (if more than two), because they are split by Python exclude_repos = os.getenv("EXCLUDED")
excluded_repos = (
{x.strip() for x in exclude_repos.split(",")} if exclude_repos else None
)
exclude_langs = os.getenv("EXCLUDED_LANGS")
excluded_langs = (
{x.strip() for x in exclude_langs.split(",")} if exclude_langs else None
) |
|
Thanks for the suggestion. All I did was add Edit: There was no error at all. It just took a really long time to index my repositories I guess. Workflow takes around 4 hours. Other than the long wait, everything is running smoothly for me :) |
Does |
|
this setting change as in the comment #70 (comment) actually solves an issue |
I followed the instructions in the README but the GitHub workflow failed. Here is some information.
My personal access token permissions
Step: generate images
Step: commit to the repo
I don't get where the problem comes from, would you please provide some suggestions?
The text was updated successfully, but these errors were encountered: