Fix secp256k1 test #26
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
|
@jacobheun This fixes the test error you were seeing. The test for loading Secp256k1 keys simply needed to be updated to mirror the new behaviour in the peer-id package, since the peer ID is computed with identity hash now. |
aknuds1
force-pushed
the
bugfix/fix-secp256k1-test
branch
from
9df9f52
to
f9cc011
Compare
vasco-santos
approved these changes
Jul 15, 2019
3 tasks
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.
Fix test for loading Secp256k1 private key, to expect the peer ID to be computed with identity hash, as this is the new behaviour in the peer-id package.