introduce optional wait_time when starting the orchestrator/relayer
#21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
we introduce optional flag
wait_timewhen starting the orchestrator/relayer, it's used to specify how long are we willing to wait for ethereum node on start.I have cleaned up some of the code, especially in
get_with_retry.rsfileI have also improved logging that was mentioned in this audit issue: GRPC or transaction errors will lead to validator slashing althea-net/cosmos-gravity-bridge#357
and most importantly, we have moved
get_gravity_idoutside of the spinning loop, so gravityID is only fetched once (at the start) and it can no longer be the reason for errors.