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
Suggestion by @PierreBesson (thanks!): if relayer starts with a bundled-version mode (i.e. no --version-mode=Auto or something like that), let's wait until chain has the bundled version before actually starting relayer. That would allow us to e.g. keep running old relayer and at the same time deploy relayer for upcoming upgrade. So when upgrade happens, we won't need to deploy our relayer manually. I thought that we may do the same because of our relayer guard (so new relayer version will keep crashing until upgrade), but there's a backoff limit to restarts => it isn't good.
The text was updated successfully, but these errors were encountered:
Suggestion by @PierreBesson (thanks!): if relayer starts with a bundled-version mode (i.e. no
--version-mode=Auto
or something like that), let's wait until chain has the bundled version before actually starting relayer. That would allow us to e.g. keep running old relayer and at the same time deploy relayer for upcoming upgrade. So when upgrade happens, we won't need to deploy our relayer manually. I thought that we may do the same because of our relayer guard (so new relayer version will keep crashing until upgrade), but there's a backoff limit to restarts => it isn't good.The text was updated successfully, but these errors were encountered: