Repository navigation
Invalid memory address or nil pointer dereference #10638
Description
From a workflow run log:
Run gh workflow run file-name.yaml \
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x1013ed6c8]
goroutine 1 [running]:
github.com/cli/cli/v2/pkg/cmd/workflow/shared.FindWorkflow(0x1400071f8c0, {0x102394160, 0x140003374a0}, {0x16f8e2900, 0x1e}, {0x1400071f8b0, 0x1, 0x1})
github.com/cli/cli/v2/pkg/cmd/workflow/shared/shared.go:139 +0x148
github.com/cli/cli/v2/pkg/cmd/workflow/shared.ResolveWorkflow({0x109e961a8, 0x140000ce2d0}, 0x140004629a0, 0x1400071f780?, {0x102394160?, 0x140003374a0?}, 0x0?, {0x16f8e2900, 0x1e}, {0x1400071f8b0, ...})
github.com/cli/cli/v2/pkg/cmd/workflow/shared/shared.go:207 +0x22c
github.com/cli/cli/v2/pkg/cmd/workflow/run.runRun(0x1400085e5a0)
github.com/cli/cli/v2/pkg/cmd/workflow/run/run.go:273 +0x1d0
github.com/cli/cli/v2/pkg/cmd/workflow/run.NewCmdRun.func2(0x14000868008?, {0x140008b12c0?, 0x4?, 0x101435439?})
github.com/cli/cli/v2/pkg/cmd/workflow/run/run.go:128 +0x340
github.com/spf13/cobra.(*Command).execute(0x14000868008, {0x140008b1270, 0x5, 0x5})
github.com/spf13/[email protected]/command.go:985 +0x834
github.com/spf13/cobra.(*Command).ExecuteC(0x1400066c008)
github.com/spf13/[email protected]/command.go:1117 +0x344
github.com/spf13/cobra.(*Command).ExecuteContextC(...)
github.com/spf13/[email protected]/command.go:1050
github.com/cli/cli/v2/internal/ghcmd.Main()
github.com/cli/cli/v2/internal/ghcmd/cmd.go:119 +0x4b0
main.main()
github.com/cli/cli/v2/cmd/gh/main.go:10 +0x1c
Workflow code:
- name: Trigger “yadda yadda” workflow
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
gh workflow run file-name.yaml \
--repo ${{ github.repository }} \
-f tag_name=${{ github.ref_name }}Golang is like Perl but with the ability to specify the bit-depth of integers.
Activity
williammartin commentedon Mar 20, 2025
Hey @beyondcompute, thanks for creating this and sorry for the inconvenience!
Looks like a duplicate of #10519 which was fixed in #10521 and went into 2.68.0. It may not have rolled out to the actions runners when you saw this.
Please check
gh versionon your runner and if it'sv2.68.0or above, please come back and let us know!gh workflow runin GitHub Actions #10519