Running vscode tasks: cwd parameter not working "chdir(2) failed.: No such file or directory"

[freifrauvonbleifrei]

I can not run the usual vscode tasks over sftp even if they operate in the workspace root:

"options": {
                "cwd": "${workspaceRoot}"
            },

(in .vscode/tasks.json) and even if the cwd is not given.

I always get

chdir(2) failed.: No such file or directory
The terminal process terminated with exit code: 1

Is this a known issue or does it work for others?

[JustFly1984]

I have same issue, latest vscode, mac os 10.14 Mojave

[Restry]

+1

[Annihilater]

+1

[willigarneau]

+1

I got the same issue with the latest version of Mac OS (Mojave 10.14)

[ironbishop]

That's because tasks are executed locally. To add this feature (please), extension.remote.workspace.executeRemoteCommmand needs to accept arguments, which currently doesn't (I think?).

Task:

    {
        "label": "check",
        "type": "process",
        "problemMatcher": [],
        "linux":   { "command": "uname -a" },
        "windows": { "command": "hostname" }
    }

Output (remote is linux, locale is windows):

> Executing task in folder nagios: C:\Windows\system32\hostname.exe  <

The terminal process terminated with exit code: 2

Terminal will be reused by tasks, press any key to close it.

If it accepted arguments, this could be a working solution:

    {
        "label": "check",
        "type": "shell",
        "command": "${command:extension.remote.workspace.executeRemoteCommmand}",
        "problemMatcher": [],
        "args": ["hostname"]
    }

[xmine64]

I can't start internal terminal, it closes immediately with this error.