Fix beacon live updates #247
Merged
Conversation
This file contains 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
ghost
added
ghost
force-pushed
the
fix_beacon_live_updates
branch
from
71fb5e1
to
0876cc6
Compare
imnik11
approved these changes
Mar 7, 2022
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
In this change, we are fixing the realtime of the beacon chain explorer.
Also when the node was subscribed to the real time feature, it was spammed by infinite replication attestation message.
Type of change
How Has This Been Tested?
Go the http://localhost:4000/explorer/chain/beacon it should display the transaction in real time and also avoid the duplication of replication attestation message if the subscribed node is the same as the current one.