30848c0fcd
When synapse receives an event for a room its not in over federation, it double checks with the remote server to see if it is in fact in the room. This is done so that if the server has forgotten about the room (usually as a result of the database being dropped) it can recover from it. However, in the presence of state resets in large rooms, this can cause a lot of work for servers that have legitimately left. As a hacky solution that supports both cases we drop incoming events for rooms that we have explicitly left. This means that we no longer support the case of servers having forgotten that they've rejoined a room, but that is sufficiently rare that we're not going to support it for now. |
||
|---|---|---|
| .. | ||
| engines | ||
| schema | ||
| util | ||
| __init__.py | ||
| _base.py | ||
| account_data.py | ||
| appservice.py | ||
| background_updates.py | ||
| client_ips.py | ||
| deviceinbox.py | ||
| devices.py | ||
| directory.py | ||
| end_to_end_keys.py | ||
| event_federation.py | ||
| event_push_actions.py | ||
| events.py | ||
| filtering.py | ||
| keys.py | ||
| media_repository.py | ||
| openid.py | ||
| prepare_database.py | ||
| presence.py | ||
| profile.py | ||
| push_rule.py | ||
| pusher.py | ||
| receipts.py | ||
| registration.py | ||
| rejections.py | ||
| room.py | ||
| roommember.py | ||
| search.py | ||
| signatures.py | ||
| state.py | ||
| stream.py | ||
| tags.py | ||
| transactions.py | ||
| user_directory.py | ||