You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When unread messages get redacted, the room notification count sometimes does not decrease accordingly and instead gets stuck. Said differently: if a user has some unread messages in a room, and isn't looking at this room, and if these unread messages are redacted/removed by someone else, the unread count for this room usually decreases accordingly, but sometimes doesn't and gets stuck. One way to unblock/reset it is to open that room. The behaviour isn't very consistent, but very easy to repro with the steps below by repeating them once or twice if the issue doesn't surface the first time.
Repro steps:
As user A create channel 1
As user B join channel 1
As user A open another channel than channel1
As user B send 5 messages in channel1
As user A see that the notification count for channel1 is 5
As user B redact the 5 messages sent in channel1 one by one
As user A check the notification count for channel1. Sometimes the result will be 0 as expected, but sometimes it will be a number between 1 and 5 which isn't expected. If the notification count is 0, try again the same steps until hitting the issue (may need to repeat once or twice).
By "room notification count", I mean rooms.join[“roomId”]. unread_notifications.notification_count from the /sync response.
On a stack where I have DB access, this is what appears in event_push_actions and event_push_summary in an example where 4 messages were sent, 2 redacted, and the notification count was stuck at 4 instead of 2:
select * from event_push_summary where user_id = 'userId' and room_id = 'roomId';
user_id | room_id | notif_count | stream_ordering | unread_count | last_receipt_stream_ordering | thread_id
----------------------------------------------------------------+-------------------------------------------
userId | roomId | 4 | 2226735 | 0 | 2226260 | main
So event_push_actions correctly indicates the 2 unread, but event_push_summary incorrectly indicates a notif_count of 4 instead of 2.
Steps to reproduce
Repro steps:
As user A create channel 1
As user B join channel 1
As user A open another channel than channel1
As user B send 5 messages in channel1
As user A see that the notification count for channel1 is 5
As user B redact the 5 messages sent in channel1 one by one
As user A check the notification count for channel1. Sometimes the result will be 0 as expected, but sometimes it will be a number between 1 and 5 which isn't expected. If the notification count is 0, try again the same steps until hitting the issue (may need to repeat once or twice).
This issue has been migrated from #15698.
Description
When unread messages get redacted, the room notification count sometimes does not decrease accordingly and instead gets stuck. Said differently: if a user has some unread messages in a room, and isn't looking at this room, and if these unread messages are redacted/removed by someone else, the unread count for this room usually decreases accordingly, but sometimes doesn't and gets stuck. One way to unblock/reset it is to open that room. The behaviour isn't very consistent, but very easy to repro with the steps below by repeating them once or twice if the issue doesn't surface the first time.
Repro steps:
This is reproducible on https://app.element.io/
By "room notification count", I mean
rooms.join[“roomId”]. unread_notifications.notification_count
from the/sync
response.On a stack where I have DB access, this is what appears in
event_push_actions
andevent_push_summary
in an example where 4 messages were sent, 2 redacted, and the notification count was stuck at 4 instead of 2:So
event_push_actions
correctly indicates the 2 unread, butevent_push_summary
incorrectly indicates anotif_count
of 4 instead of 2.Steps to reproduce
Repro steps:
This is reproducible on https://app.element.io/
Homeserver
matrix.org
Synapse Version
1.85.0rc1 (b=matrix-org-hotfixes,4427151a21)
Installation Method
Docker (matrixdotorg/synapse)
Database
Not sure what https://app.element.io/ is using
Workers
I don't know
Platform
Not sure what https://app.element.io/ is using
Configuration
No response
Relevant log output
Anything else that would be useful to know?
No response
The text was updated successfully, but these errors were encountered: