Open marc0olo opened 3 years ago
somehow got in stuck
aecli should not behave like this, we need a reproduction to fix this.
introduce debug option
I think it is too early to cover cli with an obvious console.logs enableable by a flag. Also, the issue may be in sdk, so console.logs would be needed there as well. I assume these logs need for cli developers to easily understand a possible bug, but as a cli developer, I don't need them yet.
I've tried to use integrated debugging capability of node and it looks not difficult to work with:
$ node --inspect ./bin/aecli-chain.js status
chrome://inspect
in Chrome and press 'inspect' for bin/aecli-chain.js
in remote targetsbin
folder in 'Sources' tab
this is a feature request of Dincho as following command he used somehow got in stuck and he has no idea where: