6.70 Retry logic broken

[Murg]

The automatic retry download is completely not working in 6.70.

A post with errored parts starts off with Retry 0, N 10 (or 9 or . N counts down to zero. And that's it. No automatic retry.

My retry count is set to 10. I set it to 11, no change.

[Quade]

My retry count is set to 10. I set it to 11, no change

I'd set it to 2.

Are the pars downloading?

[Murg]

I don't use AutoPar/Unrar.

Pars download, if I select them to download.

Setting the Retry count to 2 makes no difference. The Retry engine never starts, never attempts a retry. I can manually trigger a single retry (selecting the posts and right click Retry).


Other odd thing: if a Par/NFO, single extent post is at the bottom of a list of downloading posts, and it is downloaded, it stays in the download list until it hits the top. If you manually move the downloaded post to the top, it is properly removed from the list.

[Quade]

I'd turn autopar back on and then disable unrar.

It's designed to work with autopar enabled. That's really the only mode I test. When you disable auto-par Newsbin assumes you want to deal with things manually. I'm unclear why retries aren't retrying but it's likely because autopar is disabled.

Let me know if it's retrying with autopar enabled.


Edit: I confirmed that if you disable autopar you put the retries into manual mode. I can do something about that.

[Murg]

Yes, retry should work in manual mode.

Yes, retry works if you turn Autopar on and download the rolled up post.

However, the Pars in that set do not participate in the retry, so if there are errors in the pars, they don't get retried.

In more general terms, I don't like how autopar works, especially that I can't get to the rar files until the retries have finished, and if there aren't enough pars to fix a rar set, it just sits there, with no indication of why it isn't doing anything (and there doesn't seem to be a obvious switch option to control this).