Open thatstarcreator opened 2 months ago
I suspect what is occurring is there is a DNS timeout when util.go DownloadData calls client.get during the hourly update interval, and the resulting error bubbles up in a way that everything stops. Perhaps a retry loop could be added around this call just in case the abnormal network condition fixes itself within three or four tries (which in my case it does).
Very frequently ytarchive hits a network error of some sort. Network interruption is typically only a matter of seconds, but it causes ytarchive to immediately stop the download in progress and begin final muxing when the stream in progress hasn't actually ended. ytarchive should instead attempt to retry and resume the download. This can also occur following the timer for waiting for stream to start, in which case the download never starts despite the stream being live.
Running v0.4.0 (Aug 20, 2023) on Windows 11 23H2.
See the following output: