-
Notifications
You must be signed in to change notification settings - Fork 596
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
test: update block proposer in testing #7430
test: update block proposer in testing #7430
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 a lot for the PR @sainoe! Really appreciate the test case too, looks great.
Do you think you could target this to the main
branch and add a changelog?
Would be happy to handle backporting this to v8.5.x for you!
* increment the proposer priority of validators * update the proposer address in the current header
49f3026
to
23d9281
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.
Thank you @sainoe! Much appreciated
Absolutely, I was kind of confused by the versioning, my bad.
Thanks a lot! This shouldn't be much work. |
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.
looks clean to me, thanks for the clear description!
Trying to diagnose CI not running. Looks mergify related. |
Could try sync the branch with cosmos/main @sainoe? Sorry about this! |
@damiannolan Looks like it's good to go now! |
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.
Thank you @sainoe!
* Introduce two following changes to the `commitBlock` method in testing: * increment the proposer priority of validators * update the proposer address in the current header * fix linter (cherry picked from commit 64f33e0)
* Introduce two following changes to the `commitBlock` method in testing: * increment the proposer priority of validators * update the proposer address in the current header * fix linter (cherry picked from commit 64f33e0) # Conflicts: # testing/chain.go
* Introduce two following changes to the `commitBlock` method in testing: * increment the proposer priority of validators * update the proposer address in the current header * fix linter (cherry picked from commit 64f33e0) Co-authored-by: Simon Noetzlin <[email protected]>
* test: update block proposer in testing (#7430) * Introduce two following changes to the `commitBlock` method in testing: * increment the proposer priority of validators * update the proposer address in the current header * fix linter (cherry picked from commit 64f33e0) # Conflicts: # testing/chain.go * why did you fail us here, mergify my boy --------- Co-authored-by: Simon Noetzlin <[email protected]> Co-authored-by: DimitrisJim <[email protected]>
Description
Currently, test chains carry the same block proposer for every block. This can lead to a situation where the block proposer isn't part of the validator set, such as after being jailed. This can cause the validation of validator sets to fail in
CometBFT v0.38.12
, see ValidateBasic.This PR addresses the issue by incrementing the validator proposer priority in test chains, ensuring that the block proposer is updated in line with changes to the validator set.
closes: #XXXX
Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
docs/
).godoc
comments.Files changed
in the GitHub PR explorer.SonarCloud Report
in the comment section below once CI passes.