mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #946] Issue: Panic after failing to load an action #557
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#557
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 @ChristopherHX on GitHub (Dec 30, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/946
System information
act:catthehacker/ubuntu:act-latestactversion: 0.2.26-master (e9c4609dcasince1891c72ab1)Expected behaviour
Print a proper errormessage and don't panic.
Actual behaviour
Panic after some failures without any cleanup.
Workflow and/or repository
workflow
Steps to reproduce
act -W .\no-panic-after-failure\push.yml -vactoutputLog
EDIT 1
I'm mitigating missing cleanup due to this issue by
github.com/ChristopherHX/act@425dc96daaAct also panics if the docker daemon is unreachable.
Reason for this issue
The PR changed the meaning of the then executor to something like finally, therefore the pipeline executor won't stop on errors and continues with an invalid state. E.g. the action.yml file failed to load, then the next pipeline entry was expected to be skipped, but since it actually runs there is a null pointer access.