Fuzz: sigp/beaconfuzz#91 #7725
Merged
Fuzz: sigp/beaconfuzz#91 #7725
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nisdas
added
Fuzz
Codecov Report
@@ Coverage Diff @@
## master #7725 +/- ##
==========================================
- Coverage 62.10% 61.94% -0.17%
==========================================
Files 429 427 -2
Lines 30438 30006 -432
==========================================
- Hits 18905 18587 -318
+ Misses 8582 8502 -80
+ Partials 2951 2917 -34 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What type of PR is this?
Core Code Fix
What does this PR do? Why is it needed?
Beaconfuzz discovered that we used an incorrect epoch when validating the slashing. We would
use the proposer_slashing's epoch instead of the current epoch in the beacon state.
Which issues(s) does this PR fix?
Fixes this issue:
sigp/beacon-fuzz#91
Other notes for review