Parse keystore address without 0x prefix, fix parse error logging #2759
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 does this pull request do? Explain your changes. (required)
This resolves a bug from #2713 when parsing keystore addresses without the 0x prefix. Errors from
parseEthKeystorePath
were also not being logged, becauseerr
was only available within the scope ofif err == nil
.Specific updates (required)
starter.go
.ethcommon.HexToAddress
toethcommon.BytesToAddress(ethcommon.FromHex(address))
in parseEthKeystorePath().ethcommon.FromHex
considers the 0x prefix optional.How did you test each of these updates (required)
TestParse_ParseEthKeystorePathValidFile
Does this pull request close any open issues?
Fixes #2757
Checklist:
make
runs successfully./test.sh
pass