Add node status, peers, and filter sync progress to the CBF node screen - #66
Open
skypank-coder wants to merge 1 commit into
Open
skypank-coder wants to merge 1 commit into
skypank-coder wants to merge 1 commit into
Conversation
Contributor
Author
|
@thunderbiscuit Please review this . |
This branch has not been deployed
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
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 #50.
The CBF node screen only exposed a binary Online/Offline status and the latest known block. This surfaces the live node data the Kyoto client already tracks.
What's shown now
peer_info().Progressevents.All of the node fields reset when the node stops.
Implementation notes
WalletScreenStategainsconnectedPeersandfiltersProgress;Kyotogets apeerInfo()passthrough.Kyoto.logToLogcat(). It both logs to Logcat and updates the UI state. This has to stay a single consumer:infoLog()/warningLog()each drive their ownnext_info()/next_warning()loop, so a second collector running alongsidelogToLogcat()would have split the event stream between them.ConnectionsMet/SuccessfulHandshake) and on warnings, since those are the events that actually change it — not on every progress tick.