Félix Saparelli

For #386 TODO: - [ ] [We can only listen to SIGTSTP](https://stackoverflow.com/questions/11886812/what-is-the-difference-between-sigstop-and-sigtstp) - [ ] How do we stop ourselves after getting a SIGTSTP? - [ ] Add option at...

Tracking issue broken out of #601: - Filtering applied upstream of action throttle - don't preserve event order - so filters can do I/O or take a long time without...

Adds experimental "filter programs", which are jaq (jq-like) filters operating on individual events, with a few cool additions to the functions available, like being able to read and hash files,...

From #489. It would be a good idea to stop or downsample repeating the same runtime error over and over, especially if it's not causing issues, like in the linked...

Provide option to not fail a destroy when the stack doesn't exist

4

## Hello! - Vote on this issue by adding a 👍 reaction - If you want to implement this feature, comment to let us know (we'll work with you on...

Responding to edits should modify the original response instead of posting a new one

1

Advanced behaviour of #78. Basically what it says on the tin. No idea on how to implement that, needs investigating.

As per its source: ```rust pub fn waitpgid(pgid: Pid, waitopts: WaitOptions) -> Result { Ok(syscalls::waitpgid(pgid, waitopts)?.map(|(_, status)| status)) } ``` The first return value is the PID of the process...

Setup and kill process group instead of just immediate child

6

See how watchexec does it: https://github.com/mattgreen/watchexec/blob/master/src/process.rs The stdlib `Process` sends a `kill` syscall to the process: https://github.com/rust-lang/rust/blob/master/src/libstd/sys/unix/process/process_unix.rs#L246 However, that doesn't kill all processes, especially with servers, see passcod/cargo-watch#25. I _really_...