Erik Johnston c54db67d0e Handle inbound events from federation asynchronously (#10272) ... Fixes #9490 This will break a couple of SyTest that are expecting failures to be added to the response of a federation /send, which obviously doesn't happen now that things are asynchronous. Two drawbacks: Currently there is no logic to handle any events left in the staging area after restart, and so they'll only be handled on the next incoming event in that room. That can be fixed separately. We now only process one event per room at a time. This can be fixed up further down the line.		2021-06-29 19:55:22 +01:00
..
01ignored_user.py
02shard_send_to_device.sql
03shard_send_to_device_sequence.sql.postgres
04_event_auth_chains.sql
04_event_auth_chains.sql.postgres
04drop_account_data.sql
05cache_invalidation.sql
06chain_cover_index.sql
06shard_account_data.sql
06shard_account_data.sql.postgres
07shard_account_data_fix.sql
08delete_pushers_for_deactivated_accounts.sql
08delete_stale_pushers.sql
09rejected_events_metadata.sql
10delete_purged_chain_cover.sql
11add_knock_members_to_stats.sql	Fix schema delta to not take as long on large servers (#10227)	2021-06-22 12:00:45 +01:00
11drop_thumbnail_constraint.sql.postgres
12account_validity_token_used_ts_ms.sql
12presence_stream_instance.sql
12presence_stream_instance_seq.sql.postgres
13users_to_send_full_presence_to.sql
15locks.sql	Add a distributed lock (#10269)	2021-06-29 19:15:47 +01:00
16federation_inbound_staging.sql	Handle inbound events from federation asynchronously (#10272)	2021-06-29 19:55:22 +01:00