Handling CS Start if Redis not present #529
Merged
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.
Issue:
If you have CS setup but no redis, it will not run on startup, but if the configuration table values are updated, we catch the update & restart all
cron
. Thus, we missed this checkResolution:
Updated the place where we check if
redis
is present in thechainIndexerListener
flow.PR-Codex overview
This PR removes a conditional check for Redis availability before starting the Chain Indexer Listener in the worker module.
Detailed summary
chainIndexerListener.ts
to always check for Redis before starting the listener