Skip to content
This repository has been archived by the owner on Jul 1, 2021. It is now read-only.

Address ethereum/eth2.0-specs#673: make getting assignments more generic #301

Merged
merged 2 commits into from
Feb 26, 2019

Conversation

hwwhww
Copy link
Contributor

@hwwhww hwwhww commented Feb 22, 2019

What was wrong?

I updated this small fix during reviewing the spec PR. 😅

See spec PR: ethereum/consensus-specs#673
Pending on spec PR got merged.

How was it fixed?

Sync with the spec PR.
Now, this function can be used to get previous, current, or next epoch committee.

Cute Animal Picture

🐿

@hwwhww hwwhww changed the title Address ethereum/eth2.0-spesc#673: make getting assignments more generic Address ethereum/eth2.0-specs#673: make getting assignments more generic Feb 22, 2019
@djrtwo
Copy link
Contributor

djrtwo commented Feb 25, 2019

I updated this small fix during reviewing the spec PR.

great way to review a spec PR!

@@ -368,9 +371,22 @@ def get_next_epoch_committee_assignment(
propose a beacon block at the assigned slot.
"""
current_epoch = state.current_epoch(config.SLOTS_PER_EPOCH)
previous_epoch = state.previous_epoch(config.SLOTS_PER_EPOCH, config.GENESIS_EPOCH)
next_epoch = current_epoch + 1
Copy link
Contributor

Choose a reason for hiding this comment

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

Found a bug in the spec when I was reviewing your (correct) code
ethereum/consensus-specs#689

Copy link
Contributor Author

Choose a reason for hiding this comment

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

oh, my apologies!

@hwwhww hwwhww merged commit 6f9fe12 into ethereum:master Feb 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants