This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Random handful of redacted message events visible after joining room with history_visibility==joined #1943
Labels
T-Defect
Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
Comments
richvdh
changed the title
Random handful of redacted message events visible after joining room with history_visibility==shared
Random handful of redacted message events visible after joining room with history_visibility==joined
Feb 23, 2017
I've managed to reproduce this (again) on Synapse 0.19.3-rc2 by joining |
As far as I can recall, this has happened every single time I've joined an IRC portal room on matrix.org. It might be relevant that I'm always joining via my own HS. |
I can reproduce this since having my own homeserver. Running Synapse 0.33.9 now, it happens every time I join a new IRC room. |
This should be fixed in #4718 |
MadLittleMods
added
the
T-Defect
Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
label
Nov 10, 2021
Closing as #4718 looks merged and I don't see any further activity here ⏩ |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@travis:t2l.io
joined a room over federation; having done so, he saw two "empty" events in the timeline from before he joined: http://imgur.com/ZC1k3IL.It is expected that the events be empty - the remote federation server will have served redacted events because nobody on travis's homeserver was a member of the room in these periods. What is not expected is that travis's homeserver served them to the client over /messages.
Inspection of the database showed that the room state at each event was as expected. The problem went away after a synapse restart. This therefore appears to have been caused by a stale cache within synapse.
It is interesting to note that the events in question (
$148698101813672eDBdZ:chat.weho.st
and$14877908446723tbDHY:chat.weho.st
) were the boundary points for the federation backfill requests:The text was updated successfully, but these errors were encountered: