-
-
Notifications
You must be signed in to change notification settings - Fork 676
Task creates spurious brand new directories on disk with backslashes preceding every space #2208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
area: variables
Changes related to variables.
Comments
Confirmed that this is a regression in Thanks! |
Thanks for the quick response, but the issue has not been resolved with 3.43.3.
|
Thank you again! It no longer creates double-escaped subdirectories in 3.43.3+fc17343. It still runs commands in the wrong directory, but that might be a separate bug. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I have a Taskfile in a parent directory, and another Taskfile in a subdirectory of the parent, using the
includes
syntax.The file names / directory names contain space characters (on macOS).
When running a task from the from the sub-directory Taskfile, Task ends up creating brand new spurious directories on disk.
Looks like it’s reading the full path, escaping it incorrectly, and then passing it on to
os.MkdirAll
.This has the side-effect that Task can no longer find binaries in my chosen directory (
./my-binary
underUSER_WORKING_DIR
), because now it’s searching the wrongly-created path instead.Version
3.43.2
Operating system
macOS
Experiments Enabled
No response
Example Taskfile
The text was updated successfully, but these errors were encountered: