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

validator/client: process Sync Committee roles separately #13995

Merged
merged 13 commits into from
Jul 1, 2024

Conversation

gsora
Copy link
Contributor

@gsora gsora commented May 14, 2024

What type of PR is this?

Bug fix

What does this PR do? Why is it needed?

In a DV context, to be compatible with the proposed selection endpoint, the VC must push all partial selections to it instead of just one.

Process sync committee role separately within the RolesAt method, so that partial selections can be pushed to the DV client appropriately, if configured.

Which issues(s) does this PR fix?

No issue open for this issue as of now, as it has been detected during internal testing.

Other notes for review

@gsora gsora requested a review from a team as a code owner May 14, 2024 09:00
@CLAassistant
Copy link

CLAassistant commented May 14, 2024

CLA assistant check
All committers have signed the CLA.

In a DV context, to be compatible with the proposed selection endpoint, the VC must push all partial selections to it instead of just one.

Process sync committee role separately within the RolesAt method, so that partial selections can be pushed to the DV client appropriately, if configured.
@gsora
Copy link
Contributor Author

gsora commented May 14, 2024

Force pushed in order to update git username/email, new computer :^)

Copy link
Member

@prestonvanloon prestonvanloon left a comment

Choose a reason for hiding this comment

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

Hello! Thanks for the PR and congrats on the new computer :)

Where are the test changes? This PR does not build.

testing/util/state_test.go Outdated Show resolved Hide resolved
@gsora
Copy link
Contributor Author

gsora commented May 14, 2024

Weird, I did run the test suite on my machine and it seemed to run just fine? Will double-check and fix all the outstanding issues.

@gsora
Copy link
Contributor Author

gsora commented May 14, 2024

Found a bug in the impl! Fixing as we speak.

Process sync committee duty at slot boundary as well.
@gsora
Copy link
Contributor Author

gsora commented May 14, 2024

@prestonvanloon should be fixed now!

@gsora gsora requested a review from prestonvanloon May 14, 2024 11:04
validator/client/validator.go Outdated Show resolved Hide resolved
@rkapka
Copy link
Contributor

rkapka commented May 29, 2024

Hey @gsora , thanks a lot for the contribution! A PR got merged in the meantime causing a conflict. Can you please resolve it? The main point of the conflict and my change request is to not return errors from role assignments if possible because that will affect all roles/validators. We should only log an error and continue, if possible.

@gsora gsora requested a review from rkapka May 29, 2024 12:40
validator/client/validator.go Outdated Show resolved Hide resolved
validator/client/validator.go Outdated Show resolved Hide resolved
@gsora gsora requested a review from rkapka May 29, 2024 14:40
rkapka
rkapka previously approved these changes May 30, 2024
@rkapka rkapka enabled auto-merge May 30, 2024 04:57
auto-merge was automatically disabled June 28, 2024 13:00

Head branch was pushed to by a user without write access

@prestonvanloon
Copy link
Member

thank you so much for this PR

@prestonvanloon prestonvanloon added this pull request to the merge queue Jul 1, 2024
Merged via the queue into prysmaticlabs:develop with commit 657750b Jul 1, 2024
16 of 17 checks passed
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.

4 participants