-
Notifications
You must be signed in to change notification settings - Fork 784
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
Broadcast various requests as per #4684 #4920
Conversation
I think "none" may be a little confusing - is it not ok to have an empty string for that case? |
@xrchz but isn't disabling broadcasting by supplying bare |
🤷♀️ I think it makes more sense that way |
I don't mind the I'll try to review properly in the next little while, but seems fine at a glance |
@uvizhe Looks like cargo-fmt is failing, you can fix it with |
@michaelsproul is it ok if I shorten 'sync-committee-messages' flag value to 'sync-committee' to match enum variant? |
@uvizhe yeah I think that's fine |
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.
Looking good on the whole, just a few minor suggestions
@michaelsproul can we move further? It's not that I'm in a hurry, I just want to make sure my part is done here. |
I think we're probably good to review and test this. It would be good if you could integrate it into one of the simulator tests |
I'm at devconnect right now but should have some time to review in a bit, or worst case once I'm back in 10 days |
Regarding adding more tests, I'm afraid I can't do it in the scope of this issue. This would require mocking at least |
I think it would be relatively straightforward to adapt one of the existing simulator tests to use the broadcast flags. I can push a commit to do this shortly |
683b7bf
to
388270f
Compare
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.
I pushed those tests, using some code from #4393 (thanks @macladson). That PR will conflict slightly with this one, but I think we should merge this first as it's simpler.
@michaelsproul, I'm not sure if you noticed my last force-push |
@uvizhe yeah I did thanks, will deploy this on some testnet infra next week then we can merge I'm still on leave after devconnect and will be back next week |
before next release i hope 😁 and not too long before |
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.
This is now running on some Goerli and Sepolia validators with --broadcast subscriptions,blocks,sync-committee
and seems to be working well. I'll continue rolling it out on our infra ahead of the next release.
Let's merge!
Issue Addressed
Addresses #4684
Proposed Changes
Adds to a validator client
--broadcast
option taking multiple possible values.Additional Info
I included a commit with multiple flags to make it possible to assess which variant fits better (because single option adds complexity to the code).