fix: add instantiating indexer status, and display error if instantiation fails #1460
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
On
develop
, when indexer instantiation fails,forc index status
will display the last status from the database. This may berunning
,Indexed 12345 blocks
.This PR adds
IndexerStatusKind::Instantiating
to avoid this situation.In addition, if the indexer instantiation fails, the status is set to
error
and a proper message is displayed:Testing steps
maciej/1437-entity-find
and start the indexer:develop
, and restart the indexer without--manifest
to keep the incompatible indexer in the database.forc index status
to see the incorrect status.maciej/add-more-indexer-statuses
, and restart the indexer (again, without--manifest
).forc index status
to see the correct status and error.