"Hide Old" doesn't always work

[olog_hai]

I've been having this weird problem since upgrading from version 5 to version 6: Almost always when doubling-clicking on a group or group-of-groups, random and usually recent old posts (i.e., already downloaded or marked as old) show up. Sometimes re-selecting "Hide Old" from the drop-down helps, but they'll show up again when I re-enter the group. Deleting the posts via Shift-DEL does always work, but I hate to do that because that means they'll never show up in the future when I do a local search. Is this a known issue? I really feel like this is a bug, because if I tell the program to mark something as old, I shouldn't see it if "Hide Old" is selected.

A couple of other observations:

* Sorting by Status is very buggy. It simply doesn't work right. Try it.

* In version 5, if a post was in "Failed Download" status (because, let's say, it hit the duplicate detector), and you forced a re-download via "Download - Bypass Filters," the status would change to "Downloaded." In version 6, it will stay in "Failed Download" status. I consider this to be a bug as well.

* I usually sort by subject. Sometimes this messes up when I enter a group because it's still downloading headers after the list of posts is displayed. I have to wait a few seconds and manually click the Subject header twice to get a proper sort.

[Quade]

* Sorting by Status is very buggy. It simply doesn't work right. Try it.

Fixed in 6.50.

* In version 5, if a post was in "Failed Download" status (because, let's say, it hit the duplicate detector), and you forced a re-download via "Download - Bypass Filters," the status would change to "Downloaded." In version 6, it will stay in "Failed Download" status. I consider this to be a bug as well.

Stays failed because it's still in the failed list. If you re-added it from the failed list to the download list, it wouldn't show failed any more. I could probably revisit this and remove it from the failed list if the file downloads.



As for the sorting new data is being added to the list. My preference is to only sort when the users says to sort, not out from under whatever you're doing.

I suspect the hide old thing might be because there's a default overlap and it's always downloading a bit of the prior headers. Some servers aren't synced very well so, having an overcatches "off by a couple" post pulls from the server. How many things re-appear?

[olog_hai]

First of all, I apologize because should have posted this in "V6 Technical Support." I'm using the stable version 6.42 and found this forum via a Google search.

I see maybe a dozen or so old posts that persist in each group or group-of-groups. It doesn't sound like much, but it gets very annoying because I keep marking them as old, and they keep reappearing. Is it possible the database is corrupted? Is there some way to repair it? Again, I try to use Shift-DEL sparingly, and even so, it's not a permanent solution. Future old posts will still reappear.

I'm also affected by the problem reported elsewhere where Easynews gets "stuck" downloading headers for groups they don't carry. I have to keep opening the downloading files list and clearing out a bunch of entries. (I'm also subscribed to Astraweb and Giganews, and they don't have this problem. Is there some way to mark a group or group-of-groups not to download headers from a particular server?) This is kind of a serious problem because if I don't clear the stuck "downloading headers" entries, Newsbin will only download posts from the other 2 servers, even when I download something from a group that Easynews carries. This means that I'll use up my Giganews and Astraweb gigs faster, even though I have a large block of unused Easynews gigs. In other words (and to put it bluntly), this timeout problem is costing me money.

[olog_hai]

By the way, I'm trying out beta 6.50 and noticed that all the time stamps are 4 hours ahead (GMT?). Is there some way to adjust them to my local time zone?

[olog_hai]

And now I see in that in beta 6.50, turning off the Dup Checker in Options-Options-Advanced does not work.

EDIT: I looked more closely, and the issue isn't with the Duplicate Detector. I'm getting various failed downloads with the message "Failed Download [PAR Process] Retry Failure: Ran out of retries." I've never seen this before, and these are with posts that don't even have any associated PAR files. Downloading them again always works. How do I prevent this error? I don't want Newsbin to do any PAR checking or auto-unRARing anyway. I prefer to do it manually.

[olog_hai]

May I please get some help here? I'm using beta 6.50.

1. I keep getting intermittent and inexplicable "Failed Download [PAR Process] Retry Failure: Ran out of retries" problems. Re-downloading almost always works. I never experienced this with previous versions of Newsbin Pro. I have AutoPAR disabled.
   
2. I keep seeing old posts reappear, sometimes even after using Shift-DEL. This was also happening in the stable 6.42 release. It seems that "Display Age" and "Hide Old" don't quite work properly when entering a group, because I'm seeing old junk from 2011 even with a Display Age of 30.
   
3. Times appear to be displayed in GMT, not in my time zone (EDT).

Any help will be appreciated. Even if I have to wipe out all existing data and start fresh, I'll do it, because Newsbin has become much less usable for me.

[DThor]

Step 1 is to upgrade to beta 2 if you haven't already, see if your issues are addressed. Lots of bug fixes in it.

If getting issues isn't something you're comfortable with, you might want to bypass beta testing. This is just part of the process.

DT

[Quade]

I keep getting intermittent and inexplicable "Failed Download [PAR Process] Retry Failure: Ran out of retries" problems. Re-downloading almost always works. I never experienced this with previous versions of Newsbin Pro. I have AutoPAR disabled.

You might want turn up retries then. The default is 2 which is good if you're using autopar. Sounds like not so good if you're not. I don't ever test with autopar disabled. You never saw this before because it's new. If autopar was enabled and PAR files were read in, it wouldn't send the files to the failed list. Newsbin assumes that "no par files" = "Fail when retries are exceeded".

In the server options, I'd try setting the overlap to 1. It sounds like you might have some dead groups in the mix and a dead group with overlap will sometimes load up old posts. I wrote myself a note to look at the dead group thing. I think I can fix that in software. Not sure I can distinguish between overlap and just downloading old headers.