question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Upgraded to v1.62.0, "Mentions Only" rooms suddenly start having notification counts

See original GitHub issue

Description

I have most/all of my rooms manually set to Mentions Only, which should mean they don’t get notification counts unless I’ve been mentioned. Somewhat randomly, I’ve started getting counts on rooms periodically in Element Web, which is powered purely by what is given in /sync from the server. The rooms are not consistent, and the problem only persists for a few messages before going back to behaving properly.

I’ve also noticed that sometimes the badge gets “stuck”: even though I’ve sent and received new messages, it’s almost as if my (implied) read receipt isn’t enough to clear the unreadness of the room. There’s a 40% chance this particular point is a client issue, but worth mentioning in case that 60% chance sparks ideas server-side.

Steps to reproduce

  1. Set a room to Mentions Only
  2. Engage in conversation in that room
  3. Eventually get a grey badge (indicating unread, unnotified, message count)
  4. Continue engaging
  5. Badge goes away

Homeserver

t2l.io

Synapse Version

v1.62.0

Installation Method

pip (from PyPI)

Platform

Ubuntu server, hosted in the ✨cloud✨

Relevant log output

Unclear what would be relevant.

Anything else that would be useful to know?

This problem only started happening ~24 hours after I upgraded to v1.62.0 (from v1.61.1). It’s happened four times since then though. I updated the same day as the v1.62.0 release.

I don’t use the global push rule to set rooms to Mentions Only: when I join a new room, I click the bell on that room and change it there. My default push rules are similar to those of a brand new user: unread messages cause a badge.

The rooms this has been happening in have been in my room list for a long while (years): they are not recent joins. Not sure if relevant, but might be helpful?

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
erikjohnstoncommented, Jul 8, 2022

should I also re-run when in the middle of it happening?

Yes please! That data is interesting, but will be more interesting to compare with when its broken

0reactions
turt2livecommented, Jul 12, 2022

I think I’ve been seeing https://github.com/matrix-org/synapse/issues/13196 - closing in favour of that.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Support increasing "unread count" for rooms without ...
No one likes getting a desktop/phone notification for every message of every work room they've been invited to. Especially if you are trying...
Read more >
Update badge with push notification while app in background
My understanding is that the badge count should notify the user of what needs action, through incremented count, but this does not happen...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found