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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retry subscription if no new events #131
Retry subscription if no new events #131
Changes from all commits
c572a64
3bf2246
568786e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i was wondering would it be simpler if we on every ticker we unsubscribe/re-subscribe again instead of
lastEventTime
🤔There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm… this feels even hackier than my current hacky solution, haha.
In the worst-case scenario, if this turns out to be too complex, we could just revert the code to use polling with a 2–3 second interval. Let’s keep that as a last resort, though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we put the capacity and intervals in config?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can, but do you see any value from adjusting this value set once rolled out? i don't see reasons to change values hence left it here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep no blocker, we can make it configurable later if needed
the intervals might be nice to have b/c recently i remember before the phase 2 testnet launch the infra guys turned on the backend services to check everything but the babylon node was still not producing new blocks (as there was no validators running), in this case as no blocks are being produced the indexer would still subscribe/resubscribe every 1 minute.