Launch Extension Fails to Run When Remote Developing with Linux

[davidcooper1]

Problem Description

I've recently been trying to contribute to the repo, and I noticed an odd behavior. Even though I installed gulp globally, npm i -g gulp and can access it in the terminal, the Launch Extension launch task fails to find gulp in the preLaunchTask.

Troubleshooting Steps

I was able to build first then run Launch Extension with the preLaunchTask commented out, so I started to look at the preLaunchTask. After some fiddling, I found that setting the Linux automation profile to use interactive mode worked.

{
    "terminal.integrated.automationProfile.linux":  { "args": ["-i"], "path": "/usr/bin/bash"  }
}

Is anyone else experiencing this error with their Linux machine or other Linux terminals? I was looking for a way to set up the shell with the user's default terminal instead of a hard path, but it seems like the args and path need to be included together. I'm also unsure of what terminals this extensions contribution team aims to support.

Setup:

Host Computer:

Windows
VSCode: 1.64.2

Remote Computer (contains microsoft/vscode-arduino repo)

Linux
VSCode: 1.64.2

Additional Notes

Please let me know if more information is required, and if there is any information anyone can provide on .vscode file standards to help fix this issue.