UNREAD count is always out of sync

Only noticed it today but the count is always 1 more than the topics available.

1 Like

Mine says 13 unread and I count 13. None missing.

Been seeing it most of the morning.
May let the count go over 10 to see if is number related.

Still waiting for it to go above 10 but just took this shot after a REFRESH.

Ok so it was not a number issue.
11 items listed but 12 in display

Summat aint just quite right.

1 Like

The only way I can kind-of reproduce this is

  1. Open the forum in multiple tabs.
  2. Navigate in both tabs to "unread".
  3. In one of the tabs, read the first topic.
  4. Go back
    The tab in which you did read the topic is updated; number is one lower, the read topic disappeared.
  5. Go to the other tab. The number is updated, the topic is now "greyed out".

Is it possible that your dark theme does not not show the difference between "greyed out" and "normal"?

After reading in one tab and viewing "unread" in another without refreshing the page:

Behaviour is the same in both Firefox and Chrome; using Windows 10.

Check with windows 11 and 10 but same

What is the sense?

Is this referring to new responses

Android phone - Unread indicator works fine for me, it shows 8 and 8 in the list

Only been one arduino tab open most of the day so its not multiple tabs.

Not they greyed out either as that works fine everywhere else.

Nor is it a refresh issue as I have tried multiple refresh and odd counts stay the same.

Also did a couple of cache clears so not that either.

Bumping this as the bug is still there.

2023-06-14 at 12-48-39

So I read all my "unread" and still have an outstanding "unread".
It appears there is quite a long delay between the counts (minutes) reflecting the true count.
Maybe there is a clue in that.
Would suggest the counter for "unread" be moved closer to the actions to provide a better response time.

1 Like

The first thing to determine is whether the bug is in the Discourse framework itself or specific to the Arduino Forum. This information will allow reporting the bug via the communication channel most appropriate for efficiently bringing it to the attention of the people who are able to investigate and fix it.

Please check to see whether the fault you experience on Arduino Forum also occurs on the try.discourse.org sandbox forum provided for testing of the Discourse framework:

  1. Open https://try.discourse.org/ in your browser.
  2. Click the "Sign Up" button at the top right corner of the page.
    :exclamation: You can't use your Arduino Forum credentials to log in to try.discourse.org.
    :exclamation: try.discourse.org is reset daily, so even if you signed up for an account in the past you will still need to sign up again for this test.
  3. Sign up for an account and log in to the account you created.
  4. Perform whatever actions produce the fault here on Arduino Forum.

After doing that, please make a reply here to let me know whether you were able to reproduce the fault on try.discourse.org.

I see there is a similar report already in the Discourse bug tracker:

Note this comment from the Discourse co-founder:

So I think that if you were able to provide clear instructions for a procedure that can be followed to reliably reproduce the fault on try.discourse.org, that would be very valuable to the Discourse developers and make it much more likely that they would be able to make a fix.

Given that there are other instances then clearly it is an issue with Discourse itself.

Already suggested a work around by moving the counter routine closer to the read routine.
That action would have to be performed by Discourse @dax1

I can confirm quite a long delay between reading the last post in the list and the counter normalising.
Would expect that to also affect other counts.

It does not seem to happen on trydiscourse. but I will have to wait for the post count to climb.

Action persists in multiple browsers and in incognito mode which again suggests the issue is with Discourse.

READ.DELAY...............................................................COUNT seems to be current action.
READ.DELAY.COUNT would be a preferred method.

Actually the delay for the system to record the post as "read" is set to 4 seconds per post.

Plus, there was another bug that may have slipped into the game, but it was fixed a couple of days ago. The Arduino site was deployed yesterday.

2 Likes

Yes the difference is clearly not a problem any more.
many thanks to you and your team for better than excellent results.

:heart: :bowing_man: :+1:

1 Like

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.