Supervisor does not back off tasks that failed in a healthy state. There are a couple places where we rely on supervisor for application-level backoff, so we always want back-off. The distinction is meant to enable runnables to implement their own specific back-off logic, which we don't, so we can safely ignore it. Fixes #37 ghstack-source-id: c756381b1b1598305ae6d59b2967ca7ea35aa68f Pull Request resolved: https://github.com/certusone/wormhole/pull/64 |
||
---|---|---|
.. | ||
abi | ||
watcher.go |