Richard van der Hoff 0a7fb24716 Fix invite rejection when we have no forward-extremeties (#7980) ... Thanks to some slightly overzealous cleanup in the `delete_old_current_state_events`, it's possible to end up with no `event_forward_extremities` in a room where we have outstanding local invites. The user would then get a "no create event in auth events" when trying to reject the invite. We can hack around it by using the dangling invite as the prev event.		2020-07-30 16:58:57 +01:00
..
ui_auth	…
__init__.py	…
_base.py	…
account_data.py	…
account_validity.py	…
acme.py	…
acme_issuing_service.py	…
admin.py	…
appservice.py	…
auth.py	…
cas_handler.py	…
deactivate_account.py	…
device.py	…
devicemessage.py	Convert the device message and pagination handlers to async/await. (#7678)	2020-06-16 08:06:17 -04:00
directory.py	…
e2e_keys.py	…
e2e_room_keys.py	…
events.py	…
federation.py	…
groups_local.py	…
identity.py	…
initial_sync.py	…
message.py	…
oidc_handler.py	…
pagination.py	…
password_policy.py	…
presence.py	…
profile.py	…
read_marker.py	…
receipts.py	…
register.py	…
room.py	…
room_list.py	…
room_member.py	Fix invite rejection when we have no forward-extremeties (#7980)	2020-07-30 16:58:57 +01:00
room_member_worker.py	…
saml_handler.py	…
search.py	…
set_password.py	…
state_deltas.py	…
stats.py	…
sync.py	…
typing.py	…
user_directory.py	…