Describe the bug
When I take my project that works on my Mac, and with all three GitHub Actions (linux, Mac, Windows), then try to run it on a Linux desktop, the openResources command fails silently. (No folder opens.)
After digging in, it appears that the call to open in codeUtil.js is failing because either:
- chrome-sandbox has not had
setuid root, or
open is not passing the --no-sandbox flag.
When I modified codeUtil.js to add the flag, the tests ran as expected.
I was unable to verify that setuid would fix the issue, because I don't have root privileges on the system.
Steps to reproduce
* Write a test that uses `openResource` to open a folder. (Assert that the folder appears in explorer).
* Run the test on Linux where `vscode-extension-tester` has simply been installed with `npm install`. (No special action taken on `chrome-sandbox`.)
Logs
There are no logs, tests just fail.
Operating System
Ubuntu
Visual Studio Code
1.103.0
vscode-extension-tester
8.17.0
NodeJS
18.1.1
npm
9.2.0
Describe the bug
When I take my project that works on my Mac, and with all three GitHub Actions (linux, Mac, Windows), then try to run it on a Linux desktop, the
openResourcescommand fails silently. (No folder opens.)After digging in, it appears that the call to
openincodeUtil.jsis failing because either:setuid root, oropenis not passing the--no-sandboxflag.When I modified
codeUtil.jsto add the flag, the tests ran as expected.I was unable to verify that
setuidwould fix the issue, because I don't have root privileges on the system.Steps to reproduce
Logs
Operating System
Ubuntu
Visual Studio Code
1.103.0
vscode-extension-tester
8.17.0
NodeJS
18.1.1
npm
9.2.0