When attempting to run/debug my VSCode extension, I'm getting the following error:
The terminal process "/usr/local/bin/zsh '-c', 'npm run watch'" failed to launch (exit code: 127).
I have set terminal.integrated.shell.osx to my zsh location in settings but it’s still failing for some reason. When I run /usr/local/bin/zsh '-c', 'npm run watch' from iTerm it runs fine.
How can I fix this error?
I'm also wondering if this is the reason all my breakpoints are unbound when I set them.
Related
I have recently started writing my LaTeX documents in VScode on my Mac running Big Sur.
I am able to build my .tex files without issue using the built in "Build LaTeX project" option (the green arrow -- short cut OPT+CMD+B). When I try to build the .tex file with CMD+SHIFT+B, however, the terminal pops up with the following text:
Executing task: msbuild /property:GenerateFullPaths=true /t:build /consoleloggerparameters:NoSummary
zsh:1: command not found: msbuild
The terminal process "/bin/zsh '-c', 'msbuild /property:GenerateFullPaths=true /t:build /consoleloggerparameters:NoSummary'" failed to launch (exit code: 127).
Terminal will be reused by tasks, press any key to close it.
Despite this, the .tex file is still built as normal. My question is: why is this happening and how do I fix it?
Thanks!
When trying to open the terminal in VSCode, I've been getting the error "The terminal process failed to launch: Starting directory (cwd) "C:\Windows\Sysnative\cmd.exe" does not exist".
Error message
The command line directory is still C:\Windows\System32\cmd.exe, not sure what to do from here, has anyone else had this problem?
Thanks
I cloned that github repository on vscode, when i use f5 to run the extension i get displayed the error in the title, i did searched for the exit code error but didn't find a solution for it.
My VSCode is able to find all my tests and lets my run them from the explorer, but upon running them it is calling the wrong path. I'm using a Poetry virtual environment which is in a different path than the tests.
From the Python Test Adapter Log:
INFO pytest at 'myproject': Running pytest with arguments: --rootdir=/Users/me/Desktop/myproject , Users/me/Desktop/project/tests/db/queries/my_test.py::test_fn
INFO pytest at 'myproject': Running /Users/me/Library/Caches/pypoetry/virtualenvs/myproject-api-NEejG4ix-py3.9/bin/pytest as an executable
CRIT pytest at 'myproject': Execution of the test Users/me/Desktop/project/tests/db/queries/my_test.py::test_fn" failed: Error: Process exited with code 4: ERROR: file or directory not found:
VSCode Settings:
"python.testing.pytestPath": "/Users/me/Library/Caches/pypoetry/virtualenvs/myproject-api-NEejG4ix-py3.9/bin/pytest",
"python.testing.unittestEnabled": false,
"python.testing.pytestEnabled": true,
"python.testing.pytestArgs": ["api/tests"],
Using this VSCode extension ID: littlefoxteam.vscode-python-test-adapter
Is there another setting for setting the path when running from the test explorer extension?
I have a build steps like:
- ...
- npm install
- npm start sb:server (start http-server to serve static files)
- npm run e2e
By the npm start sb:server; it starts the server and it hangs... and doesn't go the next phase which is npm run e2e.
I would like to add a condition to npm run e2e that it should just start without looking previous phase state (failed or succeeded).
I have checked the https://learn.microsoft.com/en-us/vsts/pipelines/process/conditions?view=vsts#job-status-functions
I can't figure out what kind of command I have to set in 'custom condition' field..
Any help would be appreciated!
Every task has a "continue on error" checkbox. Check that. Then, if that task fails, it is treated as a warning, not an error. Execution of subsequent tasks will happen normally.
I suspect that the npm start sb:server must keeps running so that it can be used all the time. So the command is never finished. The workaround is using cmd task to start another cmd task and run the npm start command in new cmd.