Task Execution Fails

[andre0xFF]

Check for existing issues

• Completed

Describe the bug / provide steps to reproduce it

When creating or editing a new task and attempting to run it, the task does not execute. No terminal window appears, and the following error is logged: IOError: Failed to spawn command '/bin/zsh': Not a directory (os error 20).

Steps to Reproduce:

1. Create a new task with the following configuration:

   {
     "label": "gitversion",
     "command": "docker run -it gittools/gitversion:5.12.0"
   }

2. Attempt to run the task.
3. Observe that no terminal window appears and the task does not execute.

Expected Result:
The task should run successfully, and a terminal window should appear showing the output of the command.

Actual Result:
The task does not run, and no terminal window appears.

Environment

Zed: v0.161.2 (Zed)
OS: macOS 14.2.1
Memory: 16 GiB
Architecture: aarch64

If applicable, add mockups / screenshots to help explain present your vision of the feature

No response

If applicable, attach your Zed.log file to this issue.

Zed.log

2024-11-15T09:52:24.174063Z [ERROR] Working directory: /Users/user/.config/zed/tasks.json Shell command: `/bin/zsh -i -c docker run -it gittools/gitversion:5.12.0`, IOError: Failed to spawn command '/bin/zsh': Not a directory (os error 20)

Caused by:
    Failed to spawn command '/bin/zsh': Not a directory (os error 20)

[SomeoneToIgnore]

Mine seems to work just fine:

without Docker:

with Docker:

---

'/bin/zsh': Not a directory

Looks like the task reuses the shell that's somehow not available to Zed (?).
What is your default shell?

If you open Zed's integrated terminal and do
echo $SHELL and file /bin/zsh, what does it output?
So the same outside Zed, in the system terminal, what does it output?

[andre0xFF]

I just want to point that task run sometimes. But usually it fails after editing the tasks file.

Here's the output:

❯ echo $SHELL
/bin/zsh

❯ file /bin/zsh
/bin/zsh: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64e:Mach-O 64-bit executable arm64e]
/bin/zsh (for architecture x86_64):	Mach-O 64-bit executable x86_64
/bin/zsh (for architecture arm64e):	Mach-O 64-bit executable arm64e

I have the same exact output on the system shell:

❯ echo $SHELL
/bin/zsh

❯ file /bin/zsh
/bin/zsh: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64e:Mach-O 64-bit executable arm64e]
/bin/zsh (for architecture x86_64):	Mach-O 64-bit executable x86_64
/bin/zsh (for architecture arm64e):	Mach-O 64-bit executable arm64e

[SomeoneToIgnore]

Thanks for more details, can reproduce this way, trying to spawn the task right after editing does nothing and there's an error in the logs.

[jeremyckahn]

I'm seeing something similar on Ubuntu as well:

Caused by:
    Failed to spawn command '/bin/bash': Not a directory (os error 20)
2024-11-15T08:48:02.952157662-06:00 [ERROR] oneshot canceled
2024-11-15T08:48:10.64456675-06:00 [WARN] Linux: Wayland: Unable to get default cursor too!
2024-11-15T08:48:10.980858258-06:00 [WARN] Linux: Wayland: Unable to get default cursor too!
2024-11-15T08:48:11.54990817-06:00 [WARN] Linux: Wayland: Unable to get default cursor too!
2024-11-15T08:48:11.566684095-06:00 [WARN] Linux: Wayland: Unable to get default cursor too!

I have Zed installed as a Flatpak. Perhaps that's related to this issue?

Additionally, I've found that I'm only able to run tasks successfully when I'm focused on the log file (/home/jeremyckahn/.var/app/dev.zed.Zed/data/zed/logs/Zed.log), not an actual code file.

[notpeter]

I can reproduce too.
I believe we are incorrectly determining the working directory for non-project files.

As a workaround, can you explicitly specify a cwd in your task definition:

{
  "label": "gitversion",
  "command": "docker run -it gittools/gitversion:5.12.0",
  "cwd": "$ZED_WORKTREE_ROOT"
}

And see if that works?

[jeremyckahn]

I can reproduce too. I believe we are incorrectly determining the working directory for non-project files.

As a workaround, can you explicitly specify a cwd in your task definition:

{
  "label": "gitversion",
  "command": "docker run -it gittools/gitversion:5.12.0",
  "cwd": "$ZED_WORKTREE_ROOT"
}

And see if that works?

I attempted to run this task and nothing happened (like all the other tasks I tried to run). Log output:

2024-11-16T09:47:02.017655328-06:00 [ERROR] Working directory: /home/jeremyckahn/.var/app/dev.zed.Zed/config/zed/tasks.json Shell command: `/bin/bash -i -c docker run -it gittools/gitversion:5.12.0`, IOError: Failed to spawn command '/bin/bash': Not a directory (os error 20)

Caused by:
    Failed to spawn command '/bin/bash': Not a directory (os error 20)