cmd/wavelet: fix unspecified wallet flag not generating random wallet #129
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 documentation states that by not specifying the
--wallet
flag, a new wallet will be randomly generated. But currently, not specifying the--wallet
flag will make Wavelet useconfig/wavelet.txt
as the wallet. In order to to generate a random wallet, the--wallet
flag has to be explicitly set to empty, e.g.:$ ./wavelet --port 3000 --api.port 9000 --wallet ""
This PR fixes this bug, so that not specifying the
--wallet
flag will generate a random wallet. It also adds integration tests forcmd/wavelet
. It requireswavelet
binary to be in$PATH
, so you need to install it if you want to run the test locally: