# Relies on a rejected PL event which will never be accepted into the DAG

# Caused by <https://github.com/matrix-org/sytest/pull/911>

Outbound federation requests missing prev_events and then asks for /state_ids and resolves the state

# We don't implement lazy membership loading yet

The only membership state included in a gapped incremental sync is for senders in the timeline

# Blacklisted out of flakiness after #1479

Invited user can reject local invite after originator leaves
Invited user can reject invite for empty room
If user leaves room, remote user changes device and rejoins we see update in /sync and /keys/changes

# Blacklisted due to flakiness

Forgotten room messages cannot be paginated

# Blacklisted due to flakiness after #1774

Local device key changes get to remote servers with correct prev_id

# we don't support groups

Remove group category
Remove group role

# Flakey

AS-ghosted users can use rooms themselves
AS-ghosted users can use rooms via AS
Events in rooms with AS-hosted room aliases are sent to AS server
Inviting an AS-hosted user asks the AS server
Accesing an AS-hosted room alias asks the AS server

# More flakey

Guest users can join guest_access rooms

# This will fail in HTTP API mode, so blacklisted for now

If a device list update goes missing, the server resyncs on the next one

# Might be a bug in the test because leaves do appear :-(

Leaves are present in non-gapped incremental syncs

# Below test was passing for the wrong reason, failing correctly since #2858
New federated private chats get full presence information (SYN-115)