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 }}
Repository navigation
Commit 535016b
Browse filesBrowse the repository at this point in the historyBrowse files
fix(consensus): exit non-zero on transient remote-signer startup failure
When the remote signer is unreachable at startup, the node's eager
connect() fails fast (unlike the runtime signing path, which retries via
sign_message_with_retry). run() caught this in its startup error arm and
called wait_for_termination(), parking the process alive-but-idle until
SIGTERM. A supervisor's restart policy never fires and a process-only
liveness check doesn't notice, so the node stays parked indefinitely even
after the signer recovers seconds later.
Return an error for transient remote-signer failures (Transport,
ServiceUnavailable, Timeout) so main exits non-zero and the supervisor
restarts the node — the same behavior already used for the EL IPC
watchdog. Permanent errors (configuration, authentication, malformed
responses) still park for manual intervention.
gRPC Status errors are intentionally excluded: the failure mode this
guards against is the eager connect() at startup, which surfaces as
Transport.
Add unit tests covering the helper through the production eyre wrap_err
chain.
0 commit comments