diff options
| author | Till <2353100+S7evinK@users.noreply.github.com> | 2022-10-11 16:04:02 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-11 16:04:02 +0200 |
| commit | 3c1474f68f2ac5e564d2bd4bd15f01d2a73f2845 (patch) | |
| tree | 05c5c35d4bae936e652c82c53228fbfac2a6aae7 /are-we-synapse-yet.list | |
| parent | 0a9aebdf011921680e5b0646bf50d7900423aa69 (diff) | |
Fix `/get_missing_events` for rooms with `joined`/`invited` history_visibility (#2787)
Sytest was using a wrong `history_visibility` for `invited`
(https://github.com/matrix-org/sytest/pull/1303), so `invited` was
passing for the wrong reason (-> defaulted to `shared`, as `invite`
wasn't understood).
This change now handles missing events like Synapse, if a server isn't
allowed to see the event, it gets a redacted version of it, making the
`get_missing_events` tests pass.
Diffstat (limited to 'are-we-synapse-yet.list')
| -rw-r--r-- | are-we-synapse-yet.list | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/are-we-synapse-yet.list b/are-we-synapse-yet.list index c776a740..81c0f804 100644 --- a/are-we-synapse-yet.list +++ b/are-we-synapse-yet.list @@ -643,7 +643,7 @@ fed Inbound federation redacts events from erased users fme Outbound federation can request missing events fme Inbound federation can return missing events for world_readable visibility fme Inbound federation can return missing events for shared visibility -fme Inbound federation can return missing events for invite visibility +fme Inbound federation can return missing events for invited visibility fme Inbound federation can return missing events for joined visibility fme outliers whose auth_events are in a different room are correctly rejected fbk Outbound federation can backfill events |