-
Notifications
You must be signed in to change notification settings - Fork 793
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.
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
Update confirmation_info RPC call to include representatives final votes for monitoring purposes #3618
Conversation
We do not currently need a system/permanent error concept in server_socket and we may never need it. We can introduce it if we ever need it.
I don't see how connection aborted is a temporary error. Connection aborted is a permanent state.
We never want to stop listening for incming sockets
…tes for monitoring purposes
Tried changing the base to develop as its unlikely to ship for V23 now as the DB5 release seems to resolve the underlying issue and this is just an RPC improvement. This has meant a number of unrelated commits which have been merged into releases/v23 have been included. Will the v23 be merged back into develop upon release? If so I will leave PR as it is is, if not I can cherrypick my 2 commits and recreate. |
102ed40
to
bd2edba
Compare
…tes for monitoring purposes
We're attempting to debug the slow cementing on the long chain on beta, at the moment its not possible to determine whether a vote received from a specific representative is final or not. We're seeing quite a few elections will total > quorum but final < quorum this may help debugging the issue.