-
Notifications
You must be signed in to change notification settings - Fork 454
Open
Description
Description
Hello,
in Element web, when all messages in a room get pruned by expiring the retention policy delay, the room is put on top of room lists (order by activity). It stays "forever", unless a new message is posted inside, which re-insert the room in good place in the ordered list.
In the states events, no event is fresher than the prune date, no clue of what causes this behavior.
NB. Issue similar to #10787 but concerned room are not in unread state.
Regards
Steps to reproduce
Tests in Element web, v. 1.11.110 & v.1.12.3
- Day 1 :
- Set a server side retention policy (say 1 day). (
default_policy/max_lifetime) - User A create 2 rooms, invites user B in each and write a message in each.
- User B accept the invitations.
- Set a server side retention policy (say 1 day). (
- Day 2 :
- User B writes a messages in one of the room.
- User A or B choose "order by activity" in his room list.
- Same user check the rooms. When the message get pruned in the room, check the room list : the empty one is on top, before the one user B just writes in.
The bug isn't present in Element-classic Android (latest, 15 october 25) nor in Element-desktop on Linux (1.12.2).
Homeserver
private server
Synapse Version
1.138
Installation Method
I don't know
Database
Workers
Multiple workers
Platform
Configuration
Message retention. Is this still experimental ?
Relevant log output
-Anything else that would be useful to know?
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels