-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pinning messages can go wrong with local room state desync #20035
Comments
The code claims to handle this correctly, the top state should show when there is more than 1 change happening at a time. @anoadragon453 can you share the view source for the |
Sure, here you are: source of `changed the pinned messages` event
|
Note that I pinned the message by simply hitting: message menu -> pin. Do you need client logs? |
Client logs won't help here, your client's room local state fell out of sync at some point, likely not recently. |
In this instance, Anoa's local room state was not synced up with reality and their act of Pinning a message caused another to be unpinned due to their client not knowing that one was in fact pinned. |
Interestingly, The source of the unpinned state event is: Source for the `unpinned a message` state event
|
Also note that no other user/device has ever manipulated pinned messages in the room. |
Question, do you need to activate something before its possible to pin a message? I tried on Desktop and on Android and its not possible. |
@natrius this repo doesn't concern Android which is a separate codebase. On Web/Desktop it is behind Labs which needs to be enabled in config.json - such as it is on develop.element.io and Element Nightly |
Pinned events have had a lot of development since this issue was reported. I'll open a new issue if I see the same behaviour. |
Steps to reproduce
Doing the following:
...the timeline then looked like:
Outcome
The copy of these messages are inconsistent with one another. I would expect the first message to read more like:
in order to match that of the unpinned message.
Operating system
Arch Linux
Application version
Element version: 1.9.5, Olm version: 3.2.3
How did you install the app?
Arch Linux repos
Homeserver
No response
Will you send logs?
No
The text was updated successfully, but these errors were encountered: