You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 26, 2022. It is now read-only.
The current version of backoff does issue a logging.error message when the backoff strategy is abandoned after reaching the maximum retry count. That log entry does create a BROKEN log entry on c-lightning, which makes test fail if allow_broken_logs is not set.
Furthermore, giving up the backoff should be a warning for us, instead of an error, since we do have a manual retry command to restart the whole process.
Backoff has recently merged a change so the log levels can be set (litl/backoff#99), but it's not yet released. Bump the dependency version once a new release is available.
The text was updated successfully, but these errors were encountered:
The current version of
backoff
does issue alogging.error
message when the backoff strategy is abandoned after reaching the maximum retry count. That log entry does create aBROKEN
log entry on c-lightning, which makes test fail ifallow_broken_logs
is not set.Furthermore, giving up the backoff should be a warning for us, instead of an error, since we do have a manual retry command to restart the whole process.
Backoff has recently merged a change so the log levels can be set (litl/backoff#99), but it's not yet released. Bump the dependency version once a new release is available.
The text was updated successfully, but these errors were encountered: