-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
actions: crash if action yaml cannot be parsed #23658
Comments
Could you provide the yaml file here? |
Yeah, I was going to report exactly this! @lunny - I got this:
I was wondering why the Action didn't trigger. No logs anywhere, but then I found it in the Gitea docker logs. In my case, I'm doing this (minimal example):
So, two issues I see here:
|
I cannot reproduce the crash in my local machine with 1.19 or main branch with your above content as a workflow file. |
I guess the author means that the act runner crashes. The log is: Hmm ... it seems that I misunderstood. Author meant that "Gitea is completely crashing" |
OK, I know the problem now. The problem is that a lot of code in You can even reproduce the crash with a very simple YAML. To fix the problem .... replace all func TestActCrash(t *testing.T) {
workflow, err := model.ReadWorkflow(bytes.NewReader([]byte(`
name: checks
on:
- asfd:
- a
`)))
assert.NoError(t, err)
workflow.On()
t.Log("Succeeded")
} Then
|
Hey Yeah, I meant the Gitea docker container, not the "act_runner" daemon. Great if you were able to find the reason for the crash! Thanks! |
I am tring to fix it on nektos/act#1705 |
Backport #23972 by @wolfogre Fix #23658. Related to https://gitea.com/gitea/act/pulls/39 Co-authored-by: Jason Song <[email protected]>
Description
When there is an error with the yaml syntax gitea crashes
Gitea Version
1.19.0
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
Git Version
No response
Operating System
No response
How are you running Gitea?
docker
Database
None
The text was updated successfully, but these errors were encountered: