feat: implement block subscription and enhance polling mechanisms for improved dashboard updates#403
Open
XJuanCarlosXD wants to merge 1 commit into
Open
feat: implement block subscription and enhance polling mechanisms for improved dashboard updates#403XJuanCarlosXD wants to merge 1 commit into
XJuanCarlosXD wants to merge 1 commit into
Conversation
… improved dashboard updates
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The explorer dashboard now auto-refreshes whenever a new block arrives, and the console is no longer flooded with errors when the RPC node is degraded. A new global block subscription detects when the chain height advances and refreshes the entire dashboard at once, so blocks, transactions, validators, and stats stay in sync without needing a manual page reload.
All RPC traffic is routed through a same-origin proxy in both production and local development, which fixes the CORS errors that appeared on deploys other than the main domain and on localhost. The blocks query was simplified to a single request per cycle instead of ten parallel ones, and all polling queries now back off automatically when the upstream node fails so the dashboard stops hammering a node that is returning 502s. The check interval was lowered to 1 second, and all internal console.log noise was removed.
@rem1niscence