-
Notifications
You must be signed in to change notification settings - Fork 146
Malformed messages: RLP decoding errors with superfluous bytes (related to compression in Ping/Pong/Disconnect) #169
Comments
Bisect result (with 0dd33ee as
All three are part of PR #108. At first glance, it seems that PR #108 made all
As noted in the PR, this contradicts EIP-706:
EDIT: Nope! The other way around: see next comment. |
@veox I know exactly why this is showing up. The reason is because that messages coming from
The PR doesn't contradict any EIP. It has followed every corner of it. There is no compression being done for the In one line, take a look at the following snippet Lines 98 to 101 in 07cabc7
This piece of the line is both the Angel and the Devil here. It makes sure that Hello Message is uncompressed which is correct. But it also makes sure that Ping, Pong, Disconnect Messages are also uncompressed which is wrong.
|
Ah, gotcha! Sorry, I panicked, and didn't read in. |
trinity-v0.1.0-alpha.20-147-g07cabc7f
(git master
, commit 07cabc7)pip freeze
): gistWhat is wrong?
Newly-occurring noisy traceback while decoding RLP:
The above IP shows many versions on ethernodes; but mostly:
Also variant with a different message:
The latter is from (possibly sending a
too_many_peers
):How can it be fixed
git bisect
to find origin of this potential regression.trinity
's end.The text was updated successfully, but these errors were encountered: