Skip to content
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

Merged
merged 22 commits into from
Jul 3, 2020
Merged

QSP-13 Only Allow Snappy P2P Encoding #6415

merged 22 commits into from
Jul 3, 2020

Conversation

rauljordan
Copy link
Contributor

What type of PR is this?

Feature

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

@rauljordan rauljordan changed the title Only Allow Snappy P2P Encoding QSP-13 Only Allow Snappy P2P Encoding Jun 26, 2020
@rauljordan rauljordan marked this pull request as ready for review June 26, 2020 16:49
@rauljordan rauljordan requested a review from a team as a code owner June 26, 2020 16:49
@rauljordan rauljordan self-assigned this Jun 26, 2020
@rauljordan rauljordan added Audit Ready For Review A pull request ready for code review labels Jun 26, 2020
terencechain
terencechain previously approved these changes Jun 26, 2020
@prestonvanloon
Copy link
Member

Note: This is being discussed in the specs repo as well, but looks like this is the right direction.

ethereum/consensus-specs#1931

Copy link
Member

@nisdas nisdas left a 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 ?

prestonvanloon
prestonvanloon previously approved these changes Jun 26, 2020
@nisdas
Copy link
Member

nisdas commented Jun 26, 2020

I think we should hold off on this until is final in the spec, it is still under discussion and hasnt been removed yet

@rauljordan
Copy link
Contributor Author

@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

@nisdas
Copy link
Member

nisdas commented Jun 29, 2020

@rauljordan sounds good then, please fix conflicts here

@codecov
Copy link

codecov bot commented Jun 29, 2020

Codecov Report

Merging #6415 into master will increase coverage by 1.02%.
The diff coverage is 68.74%.

@@            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     

nisdas
nisdas previously approved these changes Jun 30, 2020
default:
panic("Invalid Network Encoding Flag Provided")
}
return &encoder.SszNetworkEncoder{}
Copy link
Contributor

@0xKiwi 0xKiwi Jul 1, 2020

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?

@nisdas nisdas merged commit 5b708b5 into master Jul 3, 2020
@delete-merged-branch delete-merged-branch bot deleted the remove-non-snappy branch July 3, 2020 03:24
@terencechain terencechain mentioned this pull request Jul 25, 2020
15 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ready For Review A pull request ready for code review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants