[bisq-network/bisq] Tor error message at shutdown (#2465)
notifications at github.com
Fri Jan 31 09:59:14 UTC 2020
I strongly suspect tor getting cut off by the OS before the Bisq app is ready to do so - hence, the Bisq app tries to shutdown a hidden service that has already been shut down.
I recently tried to make some changes to the netlayer stack to better handle this kind of error. Made some progress, included it with the last tor update which promptly got reverted because windows clients always cause issues - and I have not been able to reproduce them - so I have not been able to "fix" that.
The thing is, the netlayer stack (including interfacing) needs love. Things are not exactly cleanly handled there. Lots of different timeouts, different handling for Windows OS, spagetti code everywhere, nasty stuff - it works somehow, but it is a minefield - touch something and you burn yourself.
I suggest creating some room in budgeting so the netlayer stack can get the love it needs. I will sketch something up...
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bisq-github