[bisq-network/bisq] Not allow bitcoinj to auto connect to localhost when localhost was not detected by client (#3783)

[chimp1984]

> Is waiting for the Jan release sufficient or is this a hotfix candidate?

I think that happens only in edge cases. At startup we connect to localhost (`BisqSetup.checkIfLocalHostNodeIsRunning`) on the default port and if that succeeds we set a flag to use local Bitcoin Core. There seems to be cases where that check fails and we should find out what causes that. I could imagine some race conditions when both Bisq and Bitcoin Core are start up at same time could cause that as well if Bitcoin Core is syncing (this should be detected as well as BitcoinJ cannot sync reliably then). 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/pull/3783#issuecomment-565285580
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191212/c248de84/attachment.html>