hedera-local-node
hedera-local-node copied to clipboard
Add a verbose option when starting up
Problem
There are some issues that arise when starting up the hedera-local-node
but is really hard to figure it out since the output of the commands are destroyed into null
or /dev/null
Example, when a port is already binded. like in this ticket: https://github.com/hashgraph/hedera-local-node/issues/411
Solution
Add an argument --verbose
that allows the user to see the output of all the executed sub-commands, and hence is easier to troubleshoot and find out the root cause of the issue.
Alternatives
No response