newsbin.com

Noticed this for awhile but I thought it would sort itself out over time.

I'm finding with a number of groups I regularly grab headers (both in folders and individual) that some, but not all, newly downloaded headers aren't being highlighted green and are instead going straight to 'old'. I usually have 'Hide Old' set and only accidentally found out I was missing seeing some new files. I can't work out whether there's anything specific about the headers that are doing this. Database problem or something else?

Never seen it. I have auto-mark old enabled, so when headers are loaded, they're marked old on disk, but stay green for that session, until I reload them. Might want to check you don't have that enabled.

DT

I wonder if you have the group open multiple places? They get marked old when loaded so, if you have a group open in one tab and it's also open in a group of groups tab, it's very possible it'll only be new in one place because it's opening twice and the first time marks the posts old.

I have Auto Mark Old enabled as I always liked that feature in V4 and find it easier, also I have 'Hide Old' in display settings on the tabs. I thought I'd look at what the help wiki says and certainly I 'double click' the large folders and individual groups on the group list. Anything to do with it? FYI I'm pulling headers from two servers, Astra with compression, Usenet-news without.

As I said I haven't noticed anything particular about what is and isn't being shown. If for example I check a group or folder once a day, I can find bunches of posts that should have been highlighted in the last download the day before that can only be found if I toggle the display settings to none.

I'm just guessing. I've not seen this happen myself. You probably don't have to bother pulling headers from Usenet-news unless it's got groups that AW doesn't.

Quade wrote:I'm just guessing. I've not seen this happen myself. You probably don't have to bother pulling headers from Usenet-news unless it's got groups that AW doesn't.

I'm not sure how complete Astra is currently, I do see different header counts, sometimes Astra with more, other times Usenet-news. So I've always considered it worthwhile to avoid any gaps in groups with large multipart audio files that may not have pars.

Perhaps it needs someone with a similar two or more master server setup to report whether they are getting similar behaviour.

Well I've given it a few days only downloading headers from Astra to test this out fully. Sadly, even using the latest beta, the same thing is occurring.

What's the next step?

How are you finding these posts that shouldn't have gotten marked old? With Auto-mark old set, all posts get marked old when you close a post list. Can you provide a step by step procedure of your workflow that leads to showing these posts that shouldn't have gotten marked old?

I'm running 3 servers on auto-header download every 15 minutes with auto-mark old enabled and I'm not seeing any obvious issues.

I'm finding these posts by changing up the age limit. The posts should either have been highlighted 'yesterday' (going on the basis I predominately download headers daily) or highlighted 'today'. Instead neither happens and they can only be found by changing the age to, in this example, 2 days.

99% of the time I double click on a folder of say between 2 and 35 groups, with Auto-Mark old set. Once the headers have downloaded I will toggle in Display Settings between Hide Old and None, and then browse through the posts.

FYI I first stumbled on the issue when the new post numbers for one particularly large folder of audio groups seemed rather low.

Is a post list already open when you double-click by chance? I wonder if some stuff you haven't seen yet is getting marked old when the list is reloaded after doing a double-click.

Nope, post list is closed.

How about separating the header download and show post activity? Instead of double-click, do a ctrl-g to download latest headers. When it's done, do a ctrl-l to show posts and see if it behaves differently.

Ok. . . should I do that per individual group or as a folder(s)?

I'd keep it simple and do it on individual groups then work up from there.

Alright, I'll try that and report back.