Closed kalepail closed 7 months ago
This is because when not running the isolated core we aren't displaying the core info endpoint status changes on the command line.
What we could do is display the core info endpoint status changes from the rpc server 🤔, that would be pretty simple. Or it would be simple to do that for each service always: core, horizon, rpc.
The change I proposed above is implemented in:
When running
--enable rpc
it isn't clear it's doing anything. There’s an exit code 0 and then a trying 1 minute, 2 minute, 3 minute… all the way to ~30 and then it stays up and you’re golden. Would be nice to have a bit more feedback that good things are happening while you wait. I canceled several times before walking away only to discover I just wasn't waiting long enough.