Emit clock slot event on updated currentSlot #2417
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Currently, we can run into a situation where the
clock.currentSlot
is updated but that slot's event has not yet been triggered (and important callbacks have not yet been executed).This can lead to confusing bugs, like:
Where even though the block passes validation (including that
block.slot >= clock.currentSlot
), the fork choice store isn't yet updated.Description
Update the
clock.currentSlot
getter to trigger clock events if the call results in an updated slot. This will give important slot event handlers a chance to run before the consumer of a currentSlot continues.Specifically, with regards to the above error, when the block in question is now validated (and checked against
clock.currentSlot
), the slot event handler will be called, allowing the fork choice to be updated before continuing block processing at that slot.