Decode peer ID properly when fetching peer #8883
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # beacon-chain/rpc/nodev1/node_test.go
Codecov Report
@@ Coverage Diff @@
## develop #8883 +/- ##
===========================================
- Coverage 60.83% 60.82% -0.01%
===========================================
Files 527 527
Lines 37173 37173
===========================================
- Hits 22613 22610 -3
- Misses 11319 11324 +5
+ Partials 3241 3239 -2 |
rauljordan
approved these changes
May 17, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Peer ID is not decoded properly before using it later in
GetPeerfunction. This PR corrects it.Which issues(s) does this PR fix?
N/A
Other notes for review
N/A