On Tue, 2 Jan 2018 17:19:14 +0100
wm4 wrote:
> It makes no sense to return an error after the first reconnect, and then
> somehow resume the next time it's called. Usually this will lead to
> demuxer errors. Make reconnecting block instead, until it has either
> successfully reconnected, or give
On Tue, 2 Jan 2018 17:19:14 +0100
wm4 wrote:
> It makes no sense to return an error after the first reconnect, and then
> somehow resume the next time it's called. Usually this will lead to
> demuxer errors. Make reconnecting block instead, until it has either
> successfully reconnected, or give
It makes no sense to return an error after the first reconnect, and then
somehow resume the next time it's called. Usually this will lead to
demuxer errors. Make reconnecting block instead, until it has either
successfully reconnected, or given up.
Also make the wait reasonably interruptible. Sinc
