I've at least three times hit the Bitcoin Core STOP button and had Gordian Server work on stopping the process, but not reflect that it was doing so in the UI (e.g., nothing was grayed out or changed). Among other things, this meant that you could hit STOP again and generate an error that bitcoind was not running.
I've had difficulty figuring out the exact situation for replicating this, other than starting and stopping a lot.
They were all while the startup of Bitcoin Core was in its early stages, before the blocks were being downloaded.
Twice (maybe three times?) they were right after I cleared the Bitcoin Core Log
The third time was right after I'd hit #151 and resolved it by moving the Server window.
I'm labeled this as MINOR under the theory that it only occurs in the early stages of setup, which may or may not definitively be the case. If it were able to happen more frequently, that might increase the concern.
I've at least three times hit the Bitcoin Core STOP button and had Gordian Server work on stopping the process, but not reflect that it was doing so in the UI (e.g., nothing was grayed out or changed). Among other things, this meant that you could hit STOP again and generate an error that
bitcoindwas not running.I've had difficulty figuring out the exact situation for replicating this, other than starting and stopping a lot.
I'm labeled this as MINOR under the theory that it only occurs in the early stages of setup, which may or may not definitively be the case. If it were able to happen more frequently, that might increase the concern.