* 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>
Rather than depend on a fork, let's incorporate cronexpr directly here.
Cronexpr won't ever receive updates at this point, so keeping it as a
fork so we could switch back to master is a bit pointless.
Incorporating it here into Supercronic gives us CI for free (which we
don't get in a fork), and it makes commits incorporating changes to
cronexpr clearer (since we can see the code changes instead of just a
dependency change).
If an interval if out of order, it ends up emitting 0000-00-00 00:00:00
as the "next" time, which is undesirable. I patched cronexpr to reject
such intervals, since a workaround is to use e.g. `6,7` instead of
`6-7`.
Since the rejection reason might not be super obvious, this patch also
adds support for printing the errors from cronexpr. That requires
`-debug` for now, largely because we don't know exactly what error to
print (we try various lengths and only some of the errors might be
relevant).
Fixes#63
* .travis.yml is modified to ignore `go.sum` diff, because `go mod vendor` command can change
it any time (as with go 1.14 `go mod vendor` does not require `-mod=readonly`; it's default now)
* `go.mod` and `go.sum` added
* `Gopkg.lock` and `Gopkg.toml` files are removed
* `Makefile` changed to comply with `go 1.14`. Also `-race` flag is added to check tests for race
conditions
* Data race was detected and fixed in `cron.go`
* `go` version used is `1.14.4` (already fixed behaviour on buggy kernels)
