avoid type confusion between protocol.PacketType and logging.PacketType #3108
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.
The enums have completely different meanings.
protocol.PacketType
only defines long header types, whereaslogging.PacketType
defines all different types of QUIC packets (including short header packets).This led to a bug in metrics implementation in libp2p: There, we were doing something along those lines:
This leads to wrong results, as
hdr.Type
is aprotocol.PacketType
and not alogging.PacketType
. It just compiled because we definedlogging.PacketType
as an alias forprotocol.PacketType
. With this PR, the code snippet above will fail to compile.