fix: disableCache
running out of order
#1162
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.
Description
The
disableCache
option is applied out of order. It needs to be run beforehistoricalSync.start
because this is where the cache is read.Currently, the
disableCache
option is applied afterhistoricalSync.start
, causing the cache progress to be recorded, then the cache to be pruned, which would cause the app to start from the wrong spot and eventually events to be missed.