mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #2199] fatal error: concurrent map iteration and map write #1041
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#1041
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 (Feb 3, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2199
CI log, does not happen most of the time.
@ChristopherHX commented on GitHub (Feb 3, 2024):
fatal error: concurrent map iteration an.txt
@github-actions[bot] commented on GitHub (Aug 2, 2024):
Issue is stale and will be closed in 14 days unless there is new activity
@qoomon commented on GitHub (Jul 21, 2025):
seems to be still an issue sometimes => https://github.com/qoomon/actions--parallel-steps/issues/15
@eastlondoner commented on GitHub (Jul 21, 2025):
Yes, this happens for us once or twice a day as an intermittent failure. Is it possible for us to collect more information to help debug
@ChristopherHX commented on GitHub (Jul 21, 2025):
I usually expect plain act to provide the full stack trace on such a panic, maybe @qoomon has an idea what could be the cause of the missing stacktrace.
fatal error:I forget that I created this issue, because this one is really really old and has never been debuggable.
I could create an build of act that forcefully triggers a panic like this while not helping debugging the original problem, if needed, only helpful to diagnose why the stacktrace is missing.
@ChristopherHX commented on GitHub (Jul 21, 2025):
BTW concurrent map read and map write is a sightly different error than I posted above
@ChristopherHX commented on GitHub (Jul 21, 2025):
my act version shows the stacktrace on the error with and without json
Just add this code somewhere into the nektos/act code and this will panic up to 100% of time, if not increment
234bug of actions--parallel-steps to hide the stacktrace