Story Feed Reaching End Prior to Last Post

Finally I can reproduce it! Ok I’ll have a fix in the next 24 hours I hope. Unfortunately I’m leaving on trip until next week but I’ll try to figure this one out. Thanks so much for that video!

1 Like

Thank you!

And thank you @MikeC!

1 Like

I was able to reproduce the issue when stories are read. Basically the list loader is sharing the same list as the unread stories list (which is new, instead of being pre-computed every time you load a page), which means that as you read stories, they are being removed from the unread stories list and paging skips over the stories you haven’t seen.

In other words, with 6 stories per page on individual feeds, if you were to read every story in a feed that has 50 stories, you should have 50/2 + 50/6=25+8=33 unreads left at the end. This bug I’ve identified and will fix soon enough.

Now, if you just scroll through a feed without marking it as read and you still don’t see every story, that would be a new issue that I haven’t seen yet.

Happens in Newest First as well, but only on single feeds. I believe I found the bug for folders, but I can’t deploy it until tonight. I’ll update this thread then.

Hey Samuel - just thought I’d check on the status of this. Is a fix still in the works?

1 Like

This should be working as expected. I just tested it out and counts are working correctly since the last two weeks.

It’s still doing it (the problem) for me

1 Like

Still happening to me too. It shows roughly half of the stories, refresh, then about half of the remaining, refresh, etc.
Example:
127 – 61 – 27 – 10 – 0
In this case, I had to refresh 3 times to see all of the stories.

1 Like

Same here. This has been happening since the redesign and it has been driving me mad.

Regards.

This bug is still present when reading Oldest First / Unread only. I fixed it for both Newest first and for All Stories. I’ll see what I can do about getting this one fixed soon.

Still having the problem on Newest-Unread

Can also confirm this remains problematic for me with Unread / Newest first.

Ok, I just launched a fix. It looks like I broke this on June 23rd, so about a month of this happening. But now both Oldest first and Newest first in Unread only on single feeds should load all stories correctly. Let me know how that works out.

Seems to be fixed. Thank-you.

Hi, this appears to be fixed now. I’ve tried IOS and Firefox desktop and all unread articles are loaded in one go now.

Regards.

Agreed, seems to be fixed now, thanks @samuelclay for getting this rolled out

I still have to refresh to get more articles on some feeds (main reddit.com for example). The most I’ve had to hit refresh it once which is an improvement over the previous situation. In the second batch, I’m getting articles from yesterday so I don’t think it’s just the feed being updated, especially on a popular one like this.

Is it possible this issue has unintentionally reared its head again? This morning I have had several individual fees (all unread-newest) that took multiple clicks to read through.

Looks like I can replicate this for single feeds in Unread Only if I also have another browser window open to NewsBlur and that window is counting unreads. Check if you have multiple windows open. That would temporarily fix it, but I agree it should work past this. This is the last issue of the archive launch and I’m going to fix it ASAP.

You are definitely correct, I had it open on another machine in a tab. With it closed, I can no longer duplicate.