Feeds showing up unread despite being read seconds ago.

  • 10
  • Problem
  • Updated 6 years ago
Since yesterday I am seeing that a lot of feeds show multiple articles as unread (new) despite having been read. Can't see a pattern, but it is quite annoying, considering I try to get to zero unread, and I follow about 120 feeds :-(
Photo of Romit Mehta

Romit Mehta

  • 67 Posts
  • 0 Reply Likes
  • sad

Posted 8 years ago

  • 10
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
Romit, I'm in your account trying to find stories that are sticking but I can't find any. Are they in particular feeds? Has it cleared up now? I'm thinking it might have something to do with timing offsets between my servers, which might account for the shift between working and non-working in a matter of an hour.
Photo of Romit Mehta

Romit Mehta

  • 67 Posts
  • 0 Reply Likes
It may have cleared. Some examples: All About Microsoft, Official Google Blog, Geekwire, Paidcontent, etc.
Photo of Romit Mehta

Romit Mehta

  • 67 Posts
  • 0 Reply Likes
Just noticed - in my "Engadget" feed (which I have "reset" per your note earlier, many times), this story has become unread twice after I have marked it as read: http://www.engadget.com/2011/10/18/mo...
Photo of Romit Mehta

Romit Mehta

  • 67 Posts
  • 0 Reply Likes
same thing with Geekwire feed, where the first article keeps popping up as unread.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
Here's the relevant logs:

[app01] [Oct 18 18:43:00] ---> [IE ] [rpmehta*] Read story in feed: Engadget
[app01] [Oct 18 18:43:00] ---> [IE ] [rpmehta*] Marked story as read: Duplicate Story -> http://www.engadget.com/2011/10/18/mo...
[app01] [Oct 18 18:43:00] ---> [IE ] [rpmehta*] Read now date: 2011-10-18 18:43:00.396396, story_date: 2011-10-18 18:20:00, story_id: http://www.engadget.com/2011/10/18/mo....
[app01] [Oct 18 18:43:00] ---> [IE ] [rpmehta*] Subscription mark_read_date: 2011-10-18 18:20:01, oldest_unread_story_date: 2011-10-18 18:34:00
[Oct 18 18:43:00] ---> [IE ] [rpmehta*] Original read date: 2011-10-18 18:37:42.317000, story id: http://www.engadget.com/2011/10/18/mo..., story.id: 4e9dc48782108873b4000001

It shows that you read the story 6 minutes earlier (and proof that it was the same story). The problem is that when the code grabs a list of read stories, this original story is not showing up, even though it's part of the original list. It clearly has something to do with the fetching of read stories in these lines in the code: https://github.com/samuelclay/NewsBlu.... Somehow the story id is not being found.

Maybe I should hash the story id so it's easier to detect. This might be a worthwhile change I can make this weekend.
Photo of Romit Mehta

Romit Mehta

  • 67 Posts
  • 0 Reply Likes
ok, phew :-) Can you let me know when I can check next? I don't want to be in this whack-a-mole game :-(
Photo of Romit Mehta

Romit Mehta

  • 67 Posts
  • 0 Reply Likes
and paidcontent too. sigh. please ping me when it is fixed. i am to OCD-ed to keep up with this any longer :-(
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
I noticed you're using IE. Have you tried marking the story as read with Chrome? When I log in to your account I'm able to mark all of those stories as read. I'm wondering if IE is doing something odd to the story ids.
Photo of Romit Mehta

Romit Mehta

  • 67 Posts
  • 0 Reply Likes
I am going to use Safari for the next few days and see if there is a difference in behavior. Just cleaned up my current backlog.
Photo of Romit Mehta

Romit Mehta

  • 67 Posts
  • 0 Reply Likes
....and, I see an old article on winrumors.com showed up as unread in Safari as well: http://www.winrumors.com/htc-windows-...
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
I checked your account again. It looks like everything is working fine under Safari. Is that the case? If it's IE-specific, I'd be more than happy to look at it under IE, but I just want to be sure it is an IE bug.
Photo of Romit Mehta

Romit Mehta

  • 67 Posts
  • 0 Reply Likes
Yes, almost confirmed that it is an IE-related bug. With Safari, no issues with dupes. I reset IE to factory settings and started all over again, and the issue showed up immediately.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
I do all my development in Safari, and occasionally with Firefox. This means that Chrome, Safari, and FF are fully supported (as well as the iPhone app). I check IE maybe once a month, and before IE9 I certainly didn't support it. I'll see what I can do about IE, but it's less than 4% of my visitors. Priorities, man.
Photo of Romit Mehta

Romit Mehta

  • 67 Posts
  • 0 Reply Likes
Oh, that's a pity. I am not going to use a different browser for this application, unfortunately. I am following this thread. When you have it fixed, let me know and I will come back :-(

It's a pity because I really like Newsblur. But I sort of understand. Sort of, because most people are ok going to a different browser because of IE "incompatabilities". I am not, since IE9 is a first-class browser and website devs should recognize that.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
Agreed, it is a first-class browser and I intend to support it. My priorities over the next two weeks are to fix premium signups (PayPal broke them somehow, ugh), get the iPhone app shipped (again), and to fix this IE bug. It might be a week before I get to it, but it's a high priority.
Photo of Romit Mehta

Romit Mehta

  • 67 Posts
  • 0 Reply Likes
Oh, that's awesome to know (that it is a matter of "weeks"). When you said it is less than 4% of your visitors, I thought it may be relegated to the bottom of the pile and be picked up after months. Good to know that is not the case.

Let me know when you are ready for me to test it again. Happy to help out in any way I can.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
Weeks = this weekend. I'll try to get this fixed, but I can't guarantee anything because it's so intractable.
Photo of Romit Mehta

Romit Mehta

  • 67 Posts
  • 0 Reply Likes
Bumping this, my favorite (and only) topic, per your tweet :-)
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
Ahh, the old IE9 compatibility issue. I'll be honest, I looked into it briefly and couldn't reproduce it immediately, so I gave up. It may be an issue that only presents itself after reading a few feeds, but I only tested it. I need to get deep into the bowels of IE testing to get this one working. :-(
Photo of Romit Mehta

Romit Mehta

  • 67 Posts
  • 0 Reply Likes
I am willing to give you all the time you need in getting this troubleshot. Lemme know how I can help.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
Also, this issue was compounded by the fact that there were actually two issues -- one I fixed a week ago (and seems to be helping a few other users as well) and this IE bug. I'm going to keep my eye on it.
Photo of Romit Mehta

Romit Mehta

  • 67 Posts
  • 0 Reply Likes
Bumping this, my favorite (and only) topic, per your tweet :-)
Photo of Romit Mehta

Romit Mehta

  • 67 Posts
  • 0 Reply Likes
Bumping again since the frequency of this happening has gone up (again). :-(
Photo of Romit Mehta

Romit Mehta

  • 67 Posts
  • 0 Reply Likes
Willing to help out in (mostly) any way :-)

Bug is very, very annoying.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
I've identified the problem, but the solution isn't so easy. IE just stops sending those queued up read-story requests. I'm not sure why it stops sending, although it may have something to do with the fact that only a single mark_story_as_read call is allowed to go at any given time, and if other stories are read before the call comes back, then the story is queued to be sent in a batch. I can change that to just send every single read story as a single call, and I may do that for IE users.

Before I do that, are there any other IE users who have this issue? I just want to see if they are reading from feeds or from folders.
Photo of dareiff

dareiff

  • 10 Posts
  • 0 Reply Likes
I'm having this problem right now, Samuel, with a feed of newly-tagged stories from Pinboard.in.

As soon as I read them, they come back in the sidebar as new stories. I can get around it by marking the folder as read, but it starts back up again as soon as the next legitimately new story comes in.
Photo of ojiikun

ojiikun

  • 475 Posts
  • 62 Reply Likes
Not entirely sure if this is the same bug, but I thought I would chime in to say that the issue isn't strictly limited to IE.

I very regularly click on a feed, quickly shift-A to mark the whole thing as read, click to a different feed, and then moments later notice the unread count of the first feed pop back up from zero. I then go back to the original feed, shift-A it a second time, and it seems to stay dead. Happens reliably in FF ESR10.0.5
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
If you see this happening, let me know immediately and I'll take a look. Alternatively, see if Insta-fetching the feed works. But regardless, let me know.
Photo of toekneebullard

toekneebullard

  • 13 Posts
  • 1 Reply Like
I'm viewing "All Site Stories" and selecting Unread Only. It thinks for a minute, and then still displays all, and the indicator never switches to Unread.

This is on the website.
Photo of bradlby

bradlby

  • 1 Post
  • 0 Reply Likes
Using the "Mark folder as read" doesn't seem to work consistently. I've seen similar things for the single feed "Mark as read," the unread number jumps back up, but not every time. Going into the feed and mashing the "next unread" button does seem to mark the stories as read properly.