Open freifrauvonbleifrei opened 5 years ago
I have same issue, latest vscode, mac os 10.14 Mojave
+1
+1
+1
I got the same issue with the latest version of Mac OS (Mojave 10.14)
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"]
}
I can't start internal terminal, it closes immediately with this error.
I can not run the usual vscode tasks over sftp even if they operate in the workspace root:
(in .vscode/tasks.json) and even if the cwd is not given.
I always get
Is this a known issue or does it work for others?