-
Notifications
You must be signed in to change notification settings - Fork 30
chore(code)!: Remove VoteSet-based synchronization protocol #1008
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
Conversation
024dbac
to
1ab3417
Compare
Looks like GitHub Actions are completely broken at this time. Will re-run CI tomorrow. |
1ab3417
to
5de387d
Compare
a70efac
to
058acf8
Compare
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #1008 +/- ##
==========================================
- Coverage 77.61% 77.01% -0.60%
==========================================
Files 159 156 -3
Lines 16814 16047 -767
Branches 16814 16047 -767
==========================================
- Hits 13050 12358 -692
+ Misses 2887 2850 -37
+ Partials 877 839 -38
Flags with carried forward coverage won't be shown. Click here to find out more. |
@@ -39,13 +39,11 @@ pub struct Status<Ctx: Context> { | |||
#[derive_where(Clone, Debug, PartialEq, Eq)] | |||
pub enum Request<Ctx: Context> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we still want to keep this enum? Same for Response
As per #922 and #998, the VoteSet protocol is neither required nor sufficient for liveness and can therefore be removed 🎉
PR author checklist
For all contributors
RELEASE_NOTES.md
if the change warrants itBREAKING_CHANGES.md
if the change warrants itFor external contributors