-
Changes made 10/16 & 10/17
- [x] #3
- [x] #4
- [x] #5
- [x] #6
- [x] #7
Moved but not have completely fixed
- [x] Socket Setup
- [x] Client connection handling
- [x] Thread Handling
- [x] logging…
-
I am working on a CLI Application based on Quarkus and Picocli using **JLINE3**.
One command forks another application / shell script which uses "trap" to react on system signals.
Once the appli…
-
Sending QUIT OR TERM signal doesnt seem to actually exit the worker properly. When testing worker will output exiting and hang there until killed by process manager. We are using supervisord and have …
tachu updated
6 years ago
-
There's a lot of potential for double-mutability here with `&mut self` in `handle`. We should either take the reference when a signal is being handled and replace it when finished or use `&self`.
-
Currently SensorBee does not handle signals.
I think it's better to trap Ctrl-C and shutdown gracefully (i.e., call Terminate for every user-defined elements in topologies so that it can perform clea…
-
Hi everyone,
I might have run into a bit of an Edge Case.
I use the hydra-submitit plugin to launch multiple tasks on a SLURM cluster.
The configuration works, and the generated slurm submission sc…
-
### Specification
Windows handles it's signals differently. According to https://nodejs.org/docs/latest-v16.x/api/process.html#processkillpid-signal.
"On Windows, where POSIX signals do not exi…
-
The main ones are SIGINT (^C) and SIGTERM (`kill`). For CLI apps that require no special cleanup, the default handling is fine (i.e. exit immediately and let the OS cleanup).
For CLI apps that need…
-
With the improved handling of navigator generation for lazy signals in https://github.com/hyperspy/hyperspy/pull/2631, it would be nice to extend parts of this to non-lazy signals as well.
Currentl…
-
We want signals (Ctrl-C, Ctrl-D and Ctrl-Z) working in netcat before we add any of the actual features.