Skip to content
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

Closed

Conversation

MajorChump
Copy link
Contributor

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.

Matthew King and others added 21 commits May 27, 2021 20:40
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
@MajorChump MajorChump changed the base branch from releases/v23 to develop January 3, 2022 10:53
@MajorChump MajorChump changed the base branch from develop to releases/v23 January 3, 2022 10:56
@MajorChump MajorChump changed the base branch from releases/v23 to develop January 3, 2022 10:56
@MajorChump
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants