Skip to content

Conversation

@andrenerd
Copy link
Contributor

No description provided.

@guruhubb guruhubb requested a review from Sriep April 18, 2021 00:00
…er-consensus-with-unavailable-sharders-34
Copy link
Contributor

@shravanshetty1 shravanshetty1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Issue title is no longer relevant. The changes include retry mechanism for sharder request, and basic refactoring. If this was the intention it looks fine.

@andrenerd
Copy link
Contributor Author

@Sriep thanks.
cleaned up. please, review again.
ps. the long commented code blocks are legacy code. not related to the issue. so keeping them commented.

@andrenerd andrenerd requested a review from Sriep April 18, 2021 20:56
@Sriep
Copy link
Contributor

Sriep commented Apr 19, 2021

Thanks.
Resolve review issues as they are handled (There is a resolve conversation button). If the issue is not resolved that indicates it is still a problem, blocking merging.
In future, if you want to discuss a review issue, use the reply option attached to the issue.

@andrenerd
Copy link
Contributor Author

@Sriep
oops, sorry.
done. could it be merged now?

@Sriep Sriep merged commit dde8eca into master Apr 19, 2021
@Sriep Sriep deleted the blobber-consensus-with-unavailable-sharders-34 branch April 19, 2021 14:19
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.

Blobber returns 400 with misleading error message when it fails to gain sharder consensus

4 participants