-
Notifications
You must be signed in to change notification settings - Fork 745
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
[Merged by Bors] - CommitteeCache.initialized: fail early if possible #4556
[Merged by Bors] - CommitteeCache.initialized: fail early if possible #4556
Conversation
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.
Thanks for the contribution.
I don't think we will ever actually run this code, a state.validators
with a length of 2**64 - 1
would be hundreds of thousands of petabytes. However, I'm happy to merge this since it is technically/theoretically better.
Oh, could you please push an empty commit to make Github realise that I've changed the target branch 🙏 |
8157b83
to
b22d1d7
Compare
Done:) |
bors r+ |
Build failed (retrying...): |
Pull request successfully merged into unstable. Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page.
|
No description provided.