Closed neonbunny closed 3 years ago
Thanks for the report.
I changed the timeout logic to fix some timeouts in the other API calls and simplify the logic.
Com was working for me (single server in colo with a 500mbps connection) but I agree that the timeout should be more lax for the larger zones for slower transfer rates. I'll work on getting a fix out soon.
This should be fixed in v1.0.2
. Let me know if you have any other issues.
The recent timeout code change which formed v1.0.1 appears to break the download of the largest zone file (.com) when running even on a reasonably spec'ed connection (AWS EC2 system with "Up to 10Gbps" bandwidth).
Since the update, I am now seeing:
The file left on disk is considered corrupted by the zip tool, presumably because it is incomplete.