-
I got some problem when I archive my iOS app, The flowing pic shows this problem happen when Copy XCFrameworks and catch
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at /AppleInternal/…
-
### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE
- [X] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field
### Checklist
- [X] I'm reporting a bug un…
-
**Describe the bug**
There's a difference in behavior in `puma` and `pumactl` for non-Puma specific code.
I'm not sure if I'd categorize it as a bug, since I can empathize with the thought it's…
-
ch20-03 suggest that implementing drop trait will gracefuly shut down the ThreadPool when CTRL-C in effect. Which is not the case for Linux (tested on ubuntu 18.04). The default action for SIGINT is t…
-
There is an OS limitation on the size of command parameters in Linux (1/4 of stack size, explained [here](https://unix.stackexchange.com/questions/45583/argument-list-too-long-how-do-i-deal-with-it-wi…
-
Normally, if you click the terminal and press ctrl+c, that will result in SIGINT being delivered to the user's process (killing it unless they've installed a signal handler). However, if the program i…
-
Hi
while using nodeload accross many servers (dstributed onto EC2 instances), I saw strange bandwidth collapsing although my scenario was a simple "ramp up".
After investigating, the collapsing was c…
-
## Bug report
If a workflow uses any kind of reduction operator (collect, count, max, reduce, etc), it will hang forever if recursed.
### Steps to reproduce the problem
Here is a minimal exa…
-
### Observed behavior
It appears that sometimes when I call `natsConnection_PublishString`, it hangs forever. I cannot kill the program with SIGINT (Ctrl + C) and it never returns control flow to the…
-
`proc.send_signal(SIGINT)` on Windows ignores / kills process, but i would like to send Ctrl+C event to process.
[yt-dlp](https://github.com/yt-dlp/yt-dlp) handles Ctrl+C event and stops the downloadi…