Skip to content

Notify proxied validator engine of new epoch #1240

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
merged 3 commits into from
Nov 18, 2020

Conversation

kevjue
Copy link
Contributor

@kevjue kevjue commented Nov 18, 2020

Description

The proxied validator engine was not being notified of a new epoch, causing that engine to not be aware of any new validator set diffs, and consequently not assigning new validators to it's proxies and never connecting to them.

Other changes

None

Tested

  • Unit tests
  • Deployed patch to a few clabs validators and verified that they started signing all of their blocks.

Backwards compatibility

Yes.

Copy link
Contributor

@trianglesphere trianglesphere left a comment

Choose a reason for hiding this comment

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

lgtm.

@trianglesphere trianglesphere merged commit d5c0140 into master Nov 18, 2020
@trianglesphere trianglesphere deleted the kevjue/proxied_validator_new_epoch branch November 18, 2020 19:13
trianglesphere pushed a commit that referenced this pull request Nov 18, 2020
* notify proxied validator engine on new peoch

* added comment

* clarified comment

Co-authored-by: Kevin Jue <[email protected]>
mcortesi pushed a commit that referenced this pull request Nov 19, 2020
* notify proxied validator engine on new peoch

* added comment

* clarified comment

Co-authored-by: Kevin Jue <[email protected]>
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.

2 participants