Closed stricklandrbls closed 2 weeks ago
Spawning scripts in Windows has changed in a breaking way due to a high severity CVE that has been repaired in recent versions of Node.js:
And here is more details on how to fix it:
https://nodejs.org/api/child_process.html#spawning-bat-and-cmd-files-on-windows
The API function
stopProcessUsingPID(...)
is resolvingfalse
when the PID is in fact stopped.Example Screenshots
Omega Edit PID (from Data Editor server info)
VSCode Notification of Failure
I confirmed that there was no actual process running with that PID by using
ps
.Breakpoint on Function Usage Showing
false
Return Here, I'm awaiting the promise resolution and logging the output to the console. This can be seen in the lower lefthand corner of the screenshot.