Closed NathanWailes closed 5 years ago
The timeout parameter should really be passed as an optional argument to the SmartDL constructor.
Furthermore it seems that the utils.is_HTTPRange_supported
is not using the global SmartDL timeout.
I'll make a patch for that later today.
Thank you!
I've added the option. Can you check it's solving your issue?
Unfortunately it seems the server is responding quickly enough now that it isn't causing an error even with the version of pySmartDL I was using before this update you pushed, so I can't verify whether this will fix the issue if it pops up again, but I suspect it will. If I see the issue tomorrow (when there may be more load on the server) I'll be sure to try to use the constructor parameter and I'll let you know if it works or not.
Here's the link to the video if you want to test it yourself: https://staging.doohken.com/storage/4/fillervideo-skateboarding_screen.mp4
Hi Itay,
Background
The problem
URLError
exception on line 129 ofpySmartDL.py
, where it makes a call toutils.is_HTTPRange_supported(self.url)
.A potential solution
timeout
argument to theSmartDL()
call.The stack trace: