Items marked "read" ARE NOT read -- when will we get a fix?

  • 16
  • Problem
  • Updated 5 years ago
This is now officially irritating. I am a programmer. I can sympathize. But you have let this problem go on for too long.

When will we get a fix?

Thanks.
Photo of desert fox

desert fox

  • 12 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 16
Photo of Nicholas Riley

Nicholas Riley

  • 143 Posts
  • 8 Reply Likes
Samuel's been sick, as he's posted on several threads. He's made a couple of attempts which seem to fix the problems for him. Some more specific reproduction instructions on what you are doing that causes the read articles to return to unread might help.

For what it's worth, I have not seen this problem at *all*.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
I haven't been able to reproduce it at all, so I'm trying to figure out what the difference is. Please include a thorough way to reproduce the issue so that I can track it down. All of my systems look fine and my stats are showing other folks are marking stories as read using the web app.
Photo of desert fox

desert fox

  • 12 Posts
  • 0 Reply Likes
I think you guys are not trying (" I have not seen this problem at *all*) very hard to duplicate the problem and find a fix.

Capture01.jpg -- notice that in this image, new feed "Reuters: World News" has 40 "unread" items and the Icon to mark all items as read is active

Capture02.jpg -- in this image, I have marked all items in "Reuters: World News" as read, but the sidebar still shows 40 items as "unread". The active pane shows all 40 items marked as "read" and the icon to mark all items as read has disappeared.

Capture03.jpg -- in this image, I have moved focus to another news feed. The feed for "Reuters: World News" still shows 40 UNREAD items in the sidebar.

Capture04.jpg -- in this image, I have re-focussed on "Reuters: World News", and we see that the same items that were marked as read have now re-appeared as "not read", exactly like the list in capture01.jpg.

You need to work with your test bench PC's to duplicate this asap and find a fix. Create a new virtual machine on one of your dev PC's and install Firefox from scratch. Use my log-in on your virtual machine if you wish.

With all the recent posts here about this problem it is obviously a real problem.

If you can't duplicate it, then your test machines are not set up like real world machines. I will tell you (in a private email) exactly how my box here is set up if that will help you.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
Tom, can you open your developer console and see if an AJAX request was sent? From the sounds of it, you should be capable of showing a screenshot of your console.
Photo of Hampus

Hampus

  • 212 Posts
  • 31 Reply Likes
I've been having this issues intermittently as well. Sometimes a page refresh fixes it but far from reliably.

Since you asked had a look in Firefox's console after I pressed mark all as unread. Mark all as unread didn't work, nothing happened in the console. After refreshing the page many times, marking as unread finally worked. When it worked I could see two POST requests made, one to "http://newsblur.com/reader/mark_feed_..." and one to "http://newsblur.com/reader/feed_unrea...".

I also noticed that when it works I see requests to "http://newsblur.com/socket.io/1/xhr-p......" or "http://newsblur.com/socket.io/1/jsonp......" every 20 seconds or so. When mark as unread doesn't work I also do not see any of these requests.

This error "TypeError: this.transport is undefined common.js:753" also seem to be present every time I reload the page and mark all as read doesn't end up working. When it does work that error is no present.

Hope maybe some of that is useful.
Photo of Nicholas Riley

Nicholas Riley

  • 143 Posts
  • 8 Reply Likes
Tom — I am just a user of NewsBlur (though I have contributed some code to the NewsBlur iOS app, I am not responsible for it). I was simply trying to provide some background that this may not be so easy to reproduce as you may have thought.

I realize it's almost certainly a very frustrating and annoying issue to have happen to you, and I hope that Samuel is able to reproduce it soon. Sorry if I seemed to trivialize your problem; that was not my intent.
Photo of desert fox

desert fox

  • 12 Posts
  • 0 Reply Likes
@Nicholas -- no problem, and thanks for the reply.
Photo of Roberto Santana

Roberto Santana

  • 11 Posts
  • 0 Reply Likes
I've been having this issue intermittently and it sometimes goes away by Ctrl+F5, sometimes it doesn't.
Photo of desert fox

desert fox

  • 12 Posts
  • 0 Reply Likes
@Samuel -- some captures of the Firebug console. If you get better info from the regular console, I can do some grabs on that as well.

These images are in chronological order over about a 5 minute interval ....











Let me know what else might help you fix the problem.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
Tom, I don't see any mark_story_hashes_as_read calls. Were you marking stories as read during this time?
Photo of desert fox

desert fox

  • 12 Posts
  • 0 Reply Likes
@Samuel -- in case it is helpful: Capture10.jpg shows console after the *first* successful "mark all as read" in three days.



I notice a transmit to mark as read (https://www.newsblur.com/reader/mark_...) and a transmit to clear count (https://www.newsblur.com/reader/feed_...) ... both of which appear successful.
Photo of TheSeeker

TheSeeker

  • 21 Posts
  • 0 Reply Likes
This problem is hit and miss for me. Sometimes, clicking the Mark as Read button elicits the call you see below. Other times, it does absolutely nothing, i.e. no mark_feed_as_read call is made.

Photo of Roberto Santana

Roberto Santana

  • 11 Posts
  • 0 Reply Likes
I just tried the same in firebug and when clicking on "mark as read" there are no calls made.
Photo of desert fox

desert fox

  • 12 Posts
  • 0 Reply Likes
@Samuel --

"Tom, I don't see any mark_story_hashes_as_read calls. Were you marking stories as read during this time? "

No, not marking individual stories as read. Opening up a story marks it as read and decrements the unread stories count on the sidebar. I don't usually double-click or similar on individual items. Either I read it or skip it based on the headline.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
Hold on, there are two issues being conflated here. Marking individual stories as read vs. marking the entire feed as read. Please be specific when talking about these two. How exactly are you marking either stories or feeds as read? Are you hitting the checkmark button at top and it's not updating the unread count on the feed list? Because that's what I'm hearing, but I want to make sure that individual stories being opened (and implicitly marked as read) are being marked as read correctly.
Photo of TheSeeker

TheSeeker

  • 21 Posts
  • 0 Reply Likes
In my case, it's marking the entire feed as read that's not working - both by hitting the checkmark and using Shift + A.
Photo of desert fox

desert fox

  • 12 Posts
  • 0 Reply Likes
@Samuel -

I think my posts have been pretty clear, but just to confirm:

The "mark all items as read" does not work on my PC (clicking on icon at top of items list).

Opening individual items seems to work OK.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
Ok, I'm able to mark a feed as read with no issue. Does this happen immediately or after you read a few feeds? Do you read by folder or by feed? I just can't reproduce it, and judging from the logs, it seems to be working fine for others as well. I need to figure out what's different about your case.

I also logged into your account and was able to mark feeds as read (just one), so I'm still trying to figure out what's going on.
Photo of desert fox

desert fox

  • 12 Posts
  • 0 Reply Likes
@Samuel,

Just tried things again after being away for a couple of hours.

When I first cranked up Firefox and logged into Newsblur, for about 3 to 4 minutes, everything worked well. No errors when marking a feed as read; no error when opening an item (unread count decremented correctly); etc.

After about 4 to 5 minutes, we are back to totally screwed up on marking as read.

Ditto for opening Newsblur in a Private Window (Firefox).

Just an observation, but there seems to be a correlation between time logged into Newsblur and the onset of error.
Photo of desert fox

desert fox

  • 12 Posts
  • 0 Reply Likes
@Samuel,

I usually read "by feed", rarely "by folder".

I thought it might be Comcast pulling another one of their bone-head maneuvers, but I get the same results through a VPN.

I have several Firefox Extensions and Plug-ins enabled. See if any of these affect your Ajax update function:



Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
Tom, try reloading right now. I just deployed and want to ensure that it wasn't the result of a bad deploy.
Photo of n.vivia

n.vivia

  • 10 Posts
  • 0 Reply Likes
I'm having this intermittently. Sometimes, when I load the page, I get a message on the bottom left corner of my screen which says "counting takes a long time" or something similar, and then marking as read doesn't work. Then I might hit F5 and that message won't appear, and then it will work.

What goes wrong is that I click on a feed, usually in List view, I spend some time in there, and then click on the arrow at the left side of the feed's name in the list and select "Mark as read". Then the unread count doesn't refresh, and clicking on that feed again doesn't make the feeds show as read.

After a few more unread feeds show up for me, I can take screenshots of my developer console.
Photo of desert fox

desert fox

  • 12 Posts
  • 0 Reply Likes
@Samuel,

I stopped Firefox and restarted it, logged into Newsblur and checked:

Sorry amigo, no change.

BTW - I don't *always* see the "counting is hard" box, but when I do it will always fail to mark all as read.
Photo of n.vivia

n.vivia

  • 10 Posts
  • 0 Reply Likes
I just tried this on some feeds with only one unread item (because I didn't have any with more items). I was having the "counting is hard" box so I thought it wouldn't work. I had the exact same symptoms as before, except this time they automagically got marked as read after a few seconds of staying unread! Then I tried another feed ... waited more than a few seconds, nothing happened. The screenshot of that other feed is attached (I accidentally closed the first developer tools window, the one where they got marked as read later on, before I could save it)
Photo of Jerry LeDoux

Jerry LeDoux

  • 2 Posts
  • 0 Reply Likes
I've got the same or a similar issue and it doesn't matter which browser I use. It does the same thing in both Chrome and Firefox but it's not consistent. Sometime reopening the tab fixes it and sometimes it doesn't. I try to check that a folder is read and it still shows as unread. If I try to do it by site, same thing. It really is getting extremely annoying and needs to be fixed. I'm thinking of switching readers. I don't mind paying for a reader that works but I have a problem with paying for a reader that doesn't.
Photo of skew wif

skew wif

  • 4 Posts
  • 0 Reply Likes
I'm having the same problem. The checkbox at the top doesn't work. The list of stories goes grey but the folder count remains and when refreshed the stories come back.
I can mark the stories as read manually but marking 25 plus stories individually is a pain.
Another annoyance now is sometimes my feeds aren't being fetched, only when I refresh the page.
I'm using Win 8.1 and Firefox 28.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
I think I've tracked it down, but it's bizarre that this hasn't been a problem for ages. It looks like a race condition caused by loading pages of a feed while marking it as read. So the List view would cause this to come up quit ea bit, because it's always loading pages.

If you mark as read after the List view stops populating, I bet it always works. Are you marking a feed read before it has a chance to load? I'll see what I can do about fixing it, but there's nothing new here.
Photo of Hampus

Hampus

  • 212 Posts
  • 31 Reply Likes
Nope. I waited for it to load the initial items (looked and scrollbar and requests in console) before clicking mark all as read. Makes no difference.

I can even predict when loading Newsblur if it'll work or not, no need to even select a site. As noted above, several distinct differences seen between when it works and when it doesn't. "TypeError: this.transport is undefined", no regular requests to /socket.io/ and the "Counting is difficult" thing.
Photo of Panda Warrior

Panda Warrior

  • 1 Post
  • 0 Reply Likes
@Hampus, confirmed.
For me the issue appeared after Firefox was updated to 28. My be it'll help to resolve the problem.
Photo of Hampus

Hampus

  • 212 Posts
  • 31 Reply Likes
Nah, it's not Firefox. Issues occurs in Chrome as well.
Photo of desert fox

desert fox

  • 12 Posts
  • 0 Reply Likes
I have to agree with Hampus. There is no difference in my experience even after waiting for everything to load.

Ditto on the "Counting is difficult" box. If it's there, then mark all as read won't work on a single feed or a folder ... and it doesn't matter if there are 40 items or just one.

Keep trying though. I'd really like to see this fixed.
Photo of lamont

lamont

  • 5 Posts
  • 0 Reply Likes
I think I've actually seen that problem (race condition between loading pages and marking it as read) for ages... Reported it awhile ago, but I think there's been a few related bugs and you fixed something different.