exit 1 if we can't list events #5
Open
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
…asking for old blocks where it was erroring
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 were seeing strange errors talking about how we can listen for events further back than 24 hours.
The theory is that the network was done for a period of time but the process kept spinning holding onto the old block number.
When the network came back - the in memory block number is now > 24 hours old and the JSON RPC errors saying
you cannot go that far back in time- and then it death looped because it keeps asking for the old block numberIf we get any kind of error asking for block data - let's exit and let systemd restart us to ask again - this should avoid the deadlock we were seeing in prod