node status api #5767
Merged
node status api #5767
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
|
@magik6k what do you want to do with the chain health thing? |
raulk
reviewed
Mar 10, 2021
raulk
reviewed
Mar 10, 2021
|
we briefly discussed the chain health status with @magik6k and I will add some statistics on average number of blocks in the last finality (and also last 100 epochs). I will make this optional with a boolean argument, as it is potentially expensive and we might be calling status a lot for message sending. |
vyzo
force-pushed
the
feat/node-status-api
branch
from
f6d26fa to
77f58b5
Compare
|
rebased on master |
vyzo
force-pushed
the
feat/node-status-api
branch
from
77f58b5 to
522ffab
Compare
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.
Closes #5762