mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #2645] Running act under Windows leads to windows-style paths being passed to actions (potentially breaking them) #1200
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#1200
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 @edler-san on GitHub (Feb 4, 2025).
Original GitHub issue: https://github.com/nektos/act/issues/2645
Bug report info
Command used with act
Describe issue
Running the above workflow in Windows breaks in the terminal, PowerShell as well as Git Bash but works under a proper WSL2 Ubuntu bash.
My suspicion is that instead of the path that is intended to be called a "mangled" path is passed - since it uses whatever Windows returns and adds a non properly translated part to it.
src=C:\Users\user\.cache\act/browser-actions-setup-chrome@latest/would end up asC:\Users\user\.cache\actbrowser-actions-setup-chrome@latestinstead.Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
No response
@ChristopherHX commented on GitHub (Feb 4, 2025):
This one is a defect I tried to fix (e.g.
/run/act/actions/nanasess-setup-chromedriver@v2/lib/setup-chromedriver.shhas no execute permission when run on windows) and failed in review phase for reference https://github.com/nektos/act/pull/2509I can no longer recommend to turn on the feature flag
--use-new-action-cachedue to known issues not fixed in this version of act.I don't think so
@edler-san commented on GitHub (Feb 5, 2025):
This was one of the first things I tried but sadly to no avail.

I guess this means I can't use some actions windows then (
browser-actions/setup-chrome@latesthas the same issue).