* fix: random waitid error
fix https://github.com/aptible/supercronic/issues/171
* fix(reap): forward signal
* refactor: modify reaper to get supercronic exitStatus
* fix(reaper): unify signal list & fix signal forward
* chore: replace ioutil to io
* fix(test): ci timeout
* opt-out with no-reap flag
Co-authored-by: Josh Raker <48493233+joshraker@users.noreply.github.com>
* fix: typo on signal
* fix: args pass to supercronic
* fix(test): remove removed flag
* chore: remove misleading comment
---------
Co-authored-by: Josh Raker <48493233+joshraker@users.noreply.github.com>
* implement inotify support
* add integration test and fix wron crontab name for updated fsnotify monitor
* Update README.md
* fix typo in readme
---------
Co-authored-by: YannikBramkamp <74957914+YannikBramkamp@users.noreply.github.com>
This allows overlapping instances of a given job. To make this easier to
test, this also refactors `StartJob` into a helper `startFunc` to make
this functionality easier to unit test.
Co-authored-by: Pavel Popov <pavelpopov@outlook.com>
Using a (cancellable) context is a little more idiomatic than
re-implementing one using a channel, and it's a little more efficient
(since we share one context across all job goroutines, as opposed to
requiring one cancel channel per goroutine).
This will make it easier for users to debug hung jobs: rather than
requiring users to go back to when the job started to realize
(implicitly) that it's not running, this will warn at every interval
that something is wrong.
