Better solution for indexer's health check and user warning #699
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.
Fixes #697
Description
We are making decisions based on the indexer's health and there are cases where those decisions are made before the indexer is consulted. So we may end up making a bad decision based on the wrong data.
To avoid this problem I added an observable variable to indicate if the indexer was already consulted in such a way that any local query about the health state will always run after the indexer is consulted at least once.
Test scenarios
Reproduce the steps described in the issue #697
You will not get the indexer's health warning sign on Mainnet
Checklist: