-
Notifications
You must be signed in to change notification settings - Fork 1k
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
QSP-13 Only Allow Snappy P2P Encoding #6415
Conversation
Note: This is being discussed in the specs repo as well, but looks like this is the right direction. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Has this been removed from the spec ?
I think we should hold off on this until is final in the spec, it is still under discussion and hasnt been removed yet |
@nisdas in the eth2 call there was a discussion about this and teams agreed it is fine to remove. It is already removed from gossip in the spec and Danny has mentioned there is no other reason to keep it. The eth2 call was the chance for someone to speak up about it, but no one brought it up |
@rauljordan sounds good then, please fix conflicts here |
c583ce8
Codecov Report
@@ Coverage Diff @@
## master #6415 +/- ##
==========================================
+ Coverage 60.07% 61.09% +1.02%
==========================================
Files 323 355 +32
Lines 27422 28811 +1389
==========================================
+ Hits 16473 17603 +1130
- Misses 8733 8849 +116
- Partials 2216 2359 +143 |
default: | ||
panic("Invalid Network Encoding Flag Provided") | ||
} | ||
return &encoder.SszNetworkEncoder{} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is UseSnappyCompression: true
not needed here?
What type of PR is this?
What does this PR do? Why is it needed?
Currently, we allow for both snappy and non-snappy network encodings, which can lead to network partitions if someone has wrong configurations of their node or accidentally messes with the p2p encoding flags.
Which issues(s) does this PR fix?
Part of #6327