Closed laanwj closed 2 years ago
Yeah, this was a really quick bug fix I made....basically....we need to keep track of each go routine that we run, so that if then webport isn't active then onionscan will wait for the scans to finish - there is currently no mechanism for doing that.
I noticed recently that OnionScan seemed to hang after scanning when invoked via the command line, e.g.:
First thought there was a hanging thread, but it turns out that this is because the web UI is started. With
-webport 0
the old behavior returns. Should we be more verbose about this?