Page 1 of 1

NB 6.33 minor bug in "New Records" column

PostPosted: Thu Jun 14, 2012 4:59 pm
by g51
Here's a description of the steps i did and a small bug i noticed in the "New Records" column in the Groups tab.

In the Server Options screen, i have one server selected but due to incomplete posts i was getting, i have set the "Header overlap" field to 5000, just to be sure no incompletes are generated (as very well instructed by Quade in this thread).

- Select a group but don't doubleclick it.
- Download all (or new only, i don't think it matters) headers for it.
- Then double click the group in order to open a new tab for it. The newest headers are re-downloaded but when the header-download process finishes, if there are no new posts, the "New Records" column value is not set to 0. Closing and reopening NB and repeating the process has the same result. If you go to the Server Options and set the "Header overlap" field to 0 and repeat the process, the "New Records" column is normally set to 0.

P.S.: I just noticed that if you manually re-download the Latest Headers X times and you initially had a value of Y in the "New Records" column, after the X times you get a vaule of X*Y in the "New Records" column (that is, if you have a "Header overlap" <> 0 value). If you just close and re-open the group tab X times though (by double-clicking on it), you always get Y in "New Records" column.

Re: NB 6.33 minor bug in "New Records" column

PostPosted: Thu Jun 14, 2012 5:53 pm
by Quade
1 - Loading = set to zero so, it sounds like it's doing that it's supposed to be doing.

2 - With header overlap you're adding N records to the DB each time you update with nothing in the middle reseting it to zero.

I don't know if there's a fix but, I'll note it and see if anything comes to mind.

Re: NB 6.33 minor bug in "New Records" column

PostPosted: Thu Jun 14, 2012 6:26 pm
by g51
Quade wrote:With header overlap you're adding N records to the DB each time you update


Yes, but since they're not "new records", the counter should not count them at all, right? I'm guessing it's a little complex but it seems to me that regardless of "Header overlap" value, NB's behavior should be the same, that is, count only truly new records.

Anyway, hopefully you figure something out with little effort.

Re: NB 6.33 minor bug in "New Records" column

PostPosted: Thu Jun 14, 2012 7:07 pm
by Quade
I get what you're saying but, without overlap any inserts are "New" The fix is a whole 'nother level of complexity over just counting inserts. I have to decide if it's worth doing.

Re: NB 6.33 minor bug in "New Records" column

PostPosted: Fri Jun 15, 2012 3:33 am
by g51
Quade wrote:I get what you're saying but, without overlap any inserts are "New" The fix is a whole 'nother level of complexity over just counting inserts. I have to decide if it's worth doing.


Ah, i get it. NB counts the total number of headers it fetches as new, so in case of overlapping...
Yes, in that case it may be a little complex to change.