Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug]: "Consensus layer indexer is not caught up" sounds wrong #557

Closed
lukaw3d opened this issue Jun 19, 2023 · 2 comments
Closed

[Bug]: "Consensus layer indexer is not caught up" sounds wrong #557

lukaw3d opened this issue Jun 19, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@lukaw3d
Copy link
Member

lukaw3d commented Jun 19, 2023

explorer/src/locales/en/translation.json

Line 95 in a77aa3a

"unknown": "Consensus layer indexer is not caught up with the latest blocks. The number of active nodes is unknown.",

@lukaw3d lukaw3d added the bug Something isn't working label Jun 19, 2023
@lukaw3d lukaw3d changed the title [Bug]: "Consensus layer indexer is not caught up" is wrong [Bug]: "Consensus layer indexer is not caught up" sounds wrong Jun 19, 2023
@lukaw3d
Copy link
Member Author

lukaw3d commented Jun 19, 2023

wait, is the source of that information actually the consensus?

@csillag
Copy link
Contributor

csillag commented Jun 19, 2023

We display this when we get active_nodes: 0 for a runtime status. However, the indexer guys have explained to us that this typically happens when the consensus parsing is behind. So consensus is not the direct source of this information, but it's the most likely underlying cause of the situation that triggers this.

@lukaw3d lukaw3d closed this as completed Jun 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@csillag @lukaw3d