Fix minor issue in blsToExecChange message validator #13498
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.
What type of PR is this?
Bug fix
What does this PR do? Why is it needed?
postAltairMsgID
which used the wrong domain when calculating length; was usingValidSnappy
in length calculation and usingInvalidSnappy
later. It doesn't make a difference though because both domains are the same length, four bytes. Just fixing to fix.blsChange.Message
isn'tnil
before derefencing it. The gossip topic message validators, like this one, will recover from any panic. So Prysm won't crash, but it will print an annoying panic stack trace to the console.