Closed timthelion closed 7 years ago
Bulk issue close. We're closing in on the cut-over to the "r200" branch, a major version jump and substantial rewrite of core components, and most of this error handling stuff has changed (hopefully for the better!) so much that this issue has just been left in the dust.
If the issue still exists in the new versions, of course please open an issue with any new symptoms :)
(This was almost certainly some host network availability issue, and could've been improved by added more retries... but at the very least it should already print a much more sensible amount of error text in the new versions.)