RAI No visibility of unread messages - Circles are not turned bold like they should

On Happy dev Nantes, the circles with unread messages are not visible (not bold). When I'm tagged, I have the notification with the number on the name of the circle, but otherwise, the circles with unread messages aren't bold when they should be.

Old accounting Protocol

ping @jbpasquier can something be wrong with Nantes config?

I don't see anything wrong. @MattJ could there be something on prosody's side?

@Marjolaine Thanks for reporting this one. Do you confirm you ar still facing this issue?

I'm still facing the issue and today, I don't habe the number on circles I'm tagged (with an "@all"), even on Sib circles

@Marjolaine can you share a screenshot? In the initial issue you were mentioning not seeing unreads (bold channels on the left) and now if I understand it is also the case on mentions? (the count number does not display when there are unreads only). So is it both or only a problem with mentions? Are you able to see those notification in the dropdown menu with the bell?

for example, I can see in my notifications (and notifications by email) that I've been tagged on the circle HOME and the circle sib-contributors and nothing on the left menu.

Thanks @Marjolaine ! Has been able to fix it with your screenshot.

@Marjolaine Indeed, I face the same behavior.

If you log out and back in, circles are bold correctly, right?

OK @jbpasquier was too fast;.

Maybe yeah, I was. I only fixed the missing badge part, still something looks wrong with RAI/bold items.

--

This one is fixed so. applications/hubl#639 (comment 32522)

I've tried de to logout and back but I'm still facing the same issue... Circles not bold and with no badge...

now, it's working ! :)

Removing applications/hubl~165 tag, awaiting triage.

@jbpasquier @alexbourlier yes there is something that is not clear to me is that the awaiting estimation is used also on bugs like here. Can we really estimate bugs?

It'll be pretty hard usually to estimate them. At least this tag shows that Startinblox have some interest on this and may be willing to pay.

I'm OK to get this tag on bugs issues, but to keep it clear and avoid mess only after triage.

OK, let me try to tell how it was working in my head, and then we see if we are in line of if something needs adjusting. In my mind:

1. Startin'blox says Awaiting Estimation
2. The "Hubl team" says This many hours
3. Startin'blox says either Let's forget it for now then, too expensive, or Startin'blox can also say Very cool, let's fund this shit and start banging!
4. The label Funded is then applied and the "Hubl team" scrambles to make it happen :-)

I understand bug fixes are harder to assess but unless it is crazy critical, in which case it gets funded no matter what, we need an assessment to decide if we fund it or not.

Now, what do you call triage exactly in this context @jbpasquier?

Before Startin'blox could say "Awaiting estimation", there is a step where Rachel make the triage of the issue: Is it a dup? Is it something involving a resolution? What priority is this issue? [whatever else]?

To be honest I don't know what to think about this one. It's not possible to reproduce, only Nantes impacted... If it was on all instance I would say s2 for sure. What do you think @alexbourlier @jbpasquier ?

I face the same behavior most of the time. Sometimes it works for a couple of hours and then I'm back to what Marjolaine describes here.

@jbpasquier I understand your reasoning regarding triage and label distribution. Sometimes, I'll land on issues before they get triaged. Is it OK if I apply the Awaiting estimation tag, and then you guys decide what to do with it?

My fear is that if I do not do it straight when I see the issue, I lose track of it and then inertia does its things and soon enough, two weeks have past and the bug isn't fixed only because gnagnagna, life did its thing and this didn't popped up again in my radar.

I wonder if that makes sense... :-)

moved from applications/hubl#598 (moved)

mentioned in issue applications/hubl#639 (closed)

mentioned in issue #165 (closed)

assigned to @MattJ

marked #165 (closed) as a duplicate of this issue

mentioned in issue #166 (closed)

Isn't this one solved? #161 (comment 32544)

I'm not sure because with the holiday, it's very calm....

To me it is getting worse and worse. Nowadays no circle at all switch to unread. This feature has always been broken but now it just disappeared completely.

I don't know why we kept the issue specific to Happy Dev Nantes here. I'm experiencing it on https://community.startinblox.com/ as well.

Good news: the "unread circle" feature is actually working, as I've just had a bold circle which hadn't happened for days.

However it is very unreliable. I've just sift through the list of all my circles and most of those which had had some activity in them were not bold.

@MattJ @jbpasquier Are we waiting for something specific here?

Debugging from @MattJ ;-)

@MattJ

changed title from No visibility of unread messages on Happy Dev Nantes circles to No visibility of unread messages - Circles are not turned bold like they should

This circle just turned bold, so I clicked on it, but I can't see any new message in it. Tell me if that needs a specific issue.

Aurélie Jallut from https://app.paris.happy-dev.fr/ also reported the issue on Firefox on some circles only. She thought it was those of https://api.paris.happy-dev.fr/admin/ only.

Tomorrow (Tuesday) work plan: I will spend up to 3 hours debugging this tomorrow on the test3 instance that uses IndexedDB. Time budget was approved by @jbpasquier in chat.

Hurray!! Thanks for the update.

Just FYI, there are not a lot of issues on the chat side, especially on Prosody's side, and they might not be long to fix, but they are being a real blocker for many of our 300 registered users at the moment. We'll have a much better retention rate once we have them fixed. Right now, migrating people from Rocket Chat or Slack is a bit hard, but we're close.

Once we have the first batch of several hundreds weekly active users, the rest will be a piece of cake and Prosody will then soon become the most used chat server in the world Matthew!

changed time estimate to 3h