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

assigned to @XaviFP and unassigned @MattJ

Assigning to @XaviFP

MattJ
That would be entirely a frontend issue (RAI is only used to notify Converse.js when it isn't in the room)
The Converse.js code that I was previously working with is different to what is currently deployed on test3 (which I guess is expected)
The RAI plugin was listening to the 'message' event which had the 'stanza' and 'chatbox' properties. In the new code it is missing 'chatbox' and only has 'stanza'. I'm not sure if this is an intentional API break on the Converse.js side
This is a fix for that: https://matthewwild.co.uk/uploads/stdin-nHD13pBi.diff - but I don't think it's an entire fix. It looks like the event now fires before Converse.js updates the unread counter, which also causes the code to not notify

Don't storm your priorities like crazy because of this message, but to me as a daily user of Hubl, this one is the most painful issue at the moment. Everyday, I click on each circle to ensure I didn't miss anything. That's very annoying.

It is somehow a good news though, because it means the bigger problems are now solved :-)

@alexbourlier whatever the browser you don't have any unreads?

I have some on Firefox, but not many. I have none on Brave

For the record, both Lory from https://app.paris.happy-dev.fr/ and Claire from... https://app.bretagne.happy-dev.fr/ I guess, reported the issue today

Sylvain, Alice, myself: https://community.startinblox.com/ we're also facing it

@XaviFP Something pretty high on priorities. @MattJ pointed something wrong on converse side. I'm not able to reproduce on my side but @alexbourlier can, maybe you can call and check it together?

@XaviFP I believe @Cyrilthiriet is also facing the problem. If he confirms that he is, then don't hesitate to have a call with him and get the debugging info you might need with him.

If Cyril is not having the problem, I do and I'm available as much as you need for fixing this one.

removed time estimate

Guys, we are losing supportive users because of this bug. Please let's move on with this one. It is been up and financed for months. What is blocking us?

mentioned in issue #199

mentioned in merge request !70 (merged)

mentioned in commit 81047250

changed milestone to %Xmpp Cyril

Hi guys,

First of all, congrats for the impressive performance boost on the chat component. Everybody is pleased with the improvement. Bravo!

Now RAI are really not working. They are very random, and in most cases do not work at all.

Here are a few cases today where there obviously was some activity in a circle, and the circle's title didn't turn bold. I'm positive about those. Tell me if I need to provide more info on any of them, or even access to my account for debugging:

added bug-s1 label and removed bug-s2 label

I have good news for you @alexbourlier. Today JC finished an implementation of RAI directly integrated in Converse.js: https://github.com/conversejs/converse.js/blob/18e6ebe9af66b2e6ed24cf1d4c4061b0e0e302f7/docs/source/configuration.rst#L1450

Hopefully it will not be much work to update to this integrated version and drop our custom module. And hopefully no more issues...

Ah ah, indeed that sounds like honey to me! Thanks for the good news.

@jbpasquier @XaviFP Let's update?

That's rather pressing on our side, so the sooner the better.

Just so it is clear: having RAI working properly is THE chat priority at the moment.

Very close behind is history loading.

Then all the fancy features we want to thrust in

Well, @MattJ you said in your last comment that we were nearly down here ? Is there something blocking us ?

It's a pain, users are lost, they lose confidence in Hubl cause of fear of missing something, I know you know, just telling again.

I need to implement it first, I'll do that tomorrow so we can figure out where it's blocking

@manv ok thanks !

hey @manv ! How is it moving here ? do we have some progress ?

The ball for this one is currently in my court due to some server-side fixes needed, tracked at #212 (closed)

I got behind on various things due to some family stuff that came up a few weeks ago, but I'm hoping to ship the fixes this week (as early as possible).

Thanks for the update @MattJ

Don't hesitate to communicate on family stuff to @Cyrilthiriet when they come up, that helps our heartbeat.

We can't wait. Users are begging for this fix (I'm not joking)

@MattJ thanks for your reply, indeed when users come at this step it means they are entering the good way to explore Hubl and there BOOOM, UX is destroyed. It's so so so painful. Thx for your understanding on this.

Keep us posted ! thx

hey @MattJ could you tell if we are about having progress here ? Thx

Hello @MattJ I'm not too sure wich issue to follow, I've some merge passing through, but not sure wich one too follow. Are we doing good ?

This can be closed now.

@jbpasquier Where am I supposed to follow ?

@jbpasquier Are yu sure this can be closed?

RAI are still buggy. Do we have another issue?

@jbpasquier are we still supposed to follow this issue or not ?

@Cyrilthiriet No, if you want to track other bugs we still have related to RAI, there you go: #275 (closed) & #279

@jbpasquier Thx

assigned to @manv and unassigned @XaviFP

changed title from No visibility of unread messages - Circles are not turned bold like they should to RAI No visibility of unread messages - Circles are not turned bold like they should

mentioned in issue management/startinblox-feature-requests#116

closed

changed the description