mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #1306] SIGSEGV when having secrets not defined locally #708
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#708
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ikamensh on GitHub (Aug 16, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/1306
Bug report info
Command used with act
Describe issue
Not user friendly way of failing on unknown secrets.
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
No response
@egidijus commented on GitHub (Aug 23, 2022):
@ikamensh
GOARCH=amd64)for context I have similar problem.
My environment:
DOCKER_DEFAULT_PLATFORM=linux/amd64@ikamensh commented on GitHub (Aug 23, 2022):
brew install act, I at least do nothing to run it in a docker.@ChristopherHX commented on GitHub (Aug 23, 2022):
Please provide the stacktrace ( you cut the most important part of the log ) and a sample workflow.
I cannot reproduce this without additional information requested by the issue template, because I don't get a dump if the secret is not defined. You also omited where in the workflow you referenced the secret there are a lot of possible locations.
@ikamensh commented on GitHub (Sep 5, 2022):
Here is example yaml that causes the crash:
Here is the stack trace:
@ChristopherHX commented on GitHub (Sep 5, 2022):
Thank you for the additional information I see, the secrets are used as job container credentials. Using them in steps doesn't cause a crash.
Seems like the post executor should not run if starting the container fails. I'm looking into contributing a fix for the next monthly release of act.
I'm not shure how the error will look like, after I found a way to suppress the inconsistent state of the crash.