This repository has been archived by the owner on Jan 15, 2024. It is now read-only.
Persist EQS state after loop over events #1195
Merged
+22
−23
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.
This should reduce the number of writes to storage, especially if the EQS
has falled behinds and fetches multiple transactions at once.
The downside is that the EQS would have to reprocess events if an error
occurs during the loop.
The EQS log level is set to WARN because of tide-rs. As a workaround use
WARN for for EQS INFO logs.