mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #748] Issue: File paths are unquoted #474
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#474
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 @joebobmiles on GitHub (Jul 2, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/748
Originally assigned to: @catthehacker on GitHub.
System information
actversion: 0.2.23Expected behavior
Running
act, with no parameters, should run all tasks without accessing a non-existent file path that results from the truncation of a path that contains spaces.Actual behavior
actfails to quote file paths when sending commands to docker. This results in a file path that contains spaces (which is common on Windows computers) being truncated by the command line. Docker then attempts to use the truncated path, resulting in an error that causes workflows to fail.Workflow and/or repository
I made a test repository that replicates the problem.
Steps to reproduce
From scratch:
.github/workflowsdirectory..github\workflows, create a workflow file that contains the following:actwith no arguments.From repo:
Hello Worlddirectory and runactwith no arguments.actoutputLog
@nikakaltura commented on GitHub (Jul 14, 2021):
This is a serious issue. I can't run any bach commands, because my user has a space in the name
@BaileyJM02 commented on GitHub (Jul 21, 2021):
I am also having this issue, prefixing whitespace with a backward slash should fix it if quotes break some commands.
@catthehacker commented on GitHub (Aug 9, 2021):
The problem was with whole command being re-split after building it. Will be fixed by #772
--envflag to pass environment vars without file #1460