-
### Describe the bug
When I have a test using child_process, the test run and inside the extension explorer, but at a moment, the ui restart, and the test never stops.
Remarque: The test using c…
-
# Bug report
### Bug description:
#### Operating system：Win10
```python
import os
from concurrent.futures import ProcessPoolExecutor, ThreadPoolExecutor
print(f"001 at {os.getpid()}")
def task()…
-
# API Change Proposal
## Problem Statement
Currently, there is no mechanism in the Rust standard library to create a child process on Windows that does not inherit handles from the calling proce…
-
## Feature Request
The ability to reparent child processes launched from within containers or talos system-extentions.
### Description
We are creating a system extension to take some responsibi…
-
### The problem
Error: spawn C:\WINDOWS\system32\cmd.exe ENOENT
at __node_internal_captureLargerStackTrace (node:internal/errors:563:5)
at __node_internal_errnoException (node:internal/erro…
-
I'm spawning processes and using SIGSTOP/SIGCONT to suspend/resume the processes. However, I've noticed that the processes will continue living even after `'close'` having been emitted:
e.g.
```…
ronag updated
6 months ago
-
After a debugging session regarding leaking resources in tests it turned out that [a test case in the Fresh repository](https://github.com/denoland/fresh/blob/e59472e35a040880318936e8a2c03c2bf1b04783/…
-
Somehow I found that if the parsing found an error #11 and exited the ffmpeg process was still running orphan.
Example:
```
$ ffbar -ss 00:00:22 -t 1777 -i foo.mp4 -r 15 -ac 1 -ar 22050 -vf scal…
-
Comment (optional):
Error:
```
Error: spawn UNKNOWN
at ChildProcess.spawn (node:internal/child_process:413:11)
at spawn (node:child_process:768:9)
at Object.execFile (node:child_pr…
-
What is going on here? )
```
sh-5.1# port -v install gcc12 configure.compiler=clang
Warning: configured user/group macports does not exist, will build as root
---> Computing dependencies for gc…