Closed UnlimitedChild closed 1 year ago
Hi there,
Windows is not a supported OS, sorry if this was misleading. I just updated the docs to mention that.
Fix for Windows, it's working
try:
proc = stem.process.launch_tor_with_config(
take_ownership=True,
config = config,
timeout = 100, #self.args.timeout,
init_msg_handler = self.print_bootstrap,
)
torboost DEBUG [2023-05-13 23:08:50,078] Chunk (5550000000, 5599999999) already exists (size: 50000000), skipping
torboost DEBUG [2023-05-13 23:08:50,078] Worker [1] is requesting chunk (5600000000, 5649999999)
torboost DEBUG [2023-05-13 23:09:36,876] Response headers for (5600000000, 5649999999): {'Server': 'nginx/1.18.0', 'Date': 'Sat, 13 May 2023 21:09:29 GMT', 'Content-Type': 'application/octet-stream', 'Content-Length': '50000000', 'Last-Modified': 'Mon, 09 Jan 2023 00:53:47 GMT', 'Connection': 'keep-alive', 'ETag': '"73ba789b-8f2415e12"', 'Content-Range': 'bytes 5600000000-5649999999/38395780626'}
torboost INFO [2023-05-13 23:09:36,876] Worker [1] is downloading chunk (5600000000, 5649999999)
torboost INFO [2023-05-13 23:26:29,045] Worker [0] saved chunk (0, 49999999)
torboost DEBUG [2023-05-13 23:26:29,045] Chunk (5650000000, 5699999999) already exists (size: 50000000), skipping
torboost DEBUG [2023-05-13 23:26:29,045] Worker [0] is requesting chunk (5700000000, 5749999999)
Hah, nice one! I looked into the sources and it seems some sort of magic, i.e. the timeout is handled, it's just specific value for Windows and nothing else accepted... Thanks for the hint 🙂 I'll fix that.
Done
Hello,
torboost INFO [] Bootstrapping Tor process 0 stem DEBUG [] System call: tor --version (runtime: 0.02) torboost ERROR [] Could not start Tor process, conflicting ports?
raise OSError('You cannot launch tor with a timeout on Windows')
It is impossible to start Tor in Windows, what could be the problem?
Thanks!