-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Issue: panic: reflect: call of reflect.Value.Type on zero Value #760
Labels
area/workflow
Relating to workflow definitions
kind/bug
Something isn't working
meta/resolved
Issue has been fixed or valid solution has been provided (not workaround)
Projects
Milestone
Comments
same version, i get the same error when running |
In some sense it's a duplicate of #625 but since I changed it from |
catthehacker
pushed a commit
to catthehacker/act-fork
that referenced
this issue
Jul 27, 2021
fix[workflow]: default `max-parallel` fix[workflow]: default `fail-fast`, it's `true`, not `false` fix[workflow]: skipping over the job when `strategy:` is defined but `matrix:` isn't (fixes nektos#625) fix[workflow]: skip non-existing includes and hard fail on non-existing excludes fix[worfklow]: simplify Matrix decode (because I "think" I know how `yaml` works) (fixes nektos#760) fix[tests]: add test for planner and runner
catthehacker
pushed a commit
to catthehacker/act-fork
that referenced
this issue
Jul 27, 2021
fix[workflow]: default `max-parallel` fix[workflow]: default `fail-fast`, it's `true`, not `false` fix[workflow]: skipping over the job when `strategy:` is defined but `matrix:` isn't (fixes nektos#625) fix[workflow]: skip non-existing includes and hard fail on non-existing excludes fix[worfklow]: simplify Matrix decode (because I "think" I know how `yaml` works) (fixes nektos#760) fix[tests]: add test for planner and runner
catthehacker
pushed a commit
to catthehacker/act-fork
that referenced
this issue
Jul 28, 2021
fix[workflow]: default `max-parallel` fix[workflow]: default `fail-fast`, it's `true`, not `false` fix[workflow]: skipping over the job when `strategy:` is defined but `matrix:` isn't (fixes nektos#625) fix[workflow]: skip non-existing includes keys and hard fail on non-existing excludes keys fix[workflow]: simplify Matrix decode (because I "think" I know how `yaml` works) (fixes nektos#760) fix[tests]: add test for planner and runner
mergify bot
added a commit
that referenced
this issue
Aug 9, 2021
…add test (#763) * fix[workflow]: multiple fixes for workflow/matrix fix[workflow]: default `max-parallel` fix[workflow]: default `fail-fast`, it's `true`, not `false` fix[workflow]: skipping over the job when `strategy:` is defined but `matrix:` isn't (fixes #625) fix[workflow]: skip non-existing includes keys and hard fail on non-existing excludes keys fix[workflow]: simplify Matrix decode (because I "think" I know how `yaml` works) (fixes #760) fix[tests]: add test for planner and runner * fix(workflow): use yaml node for env key Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/workflow
Relating to workflow definitions
kind/bug
Something isn't working
meta/resolved
Issue has been fixed or valid solution has been provided (not workaround)
System information
act
version: 0.2.23Expected behaviour
act
does not crash when I run the following command:act --userns <my namespace> release
Actual behaviour
Running
act --userns <my namespace> release
results in the following error:Workflow and/or repository
workflow
Steps to reproduce
act
act -v --userns <namespace> release
.act
outputLog
The text was updated successfully, but these errors were encountered: