Erik Johnston 1531b214fc Add ability to wait for replication streams (#7542) ... The idea here is that if an instance persists an event via the replication HTTP API it can return before we receive that event over replication, which can lead to races where code assumes that persisting an event immediately updates various caches (e.g. current state of the room). Most of Synapse doesn't hit such races, so we don't do the waiting automagically, instead we do so where necessary to avoid unnecessary delays. We may decide to change our minds here if it turns out there are a lot of subtle races going on. People probably want to look at this commit by commit.		2020-05-22 14:21:54 +01:00
..
__init__.py	Infrastructure for a server notices room	2018-05-17 17:58:25 +01:00
consent_server_notices.py	async/await is_server_admin (#7363)	2020-05-01 15:15:36 +01:00
resource_limits_server_notices.py	Convert synapse.server_notices to async/await. (#7394)	2020-05-01 15:28:59 -04:00
server_notices_manager.py	Add ability to wait for replication streams (#7542)	2020-05-22 14:21:54 +01:00
server_notices_sender.py	async/await is_server_admin (#7363)	2020-05-01 15:15:36 +01:00
worker_server_notices_sender.py	Run Black. (#5482)	2019-06-20 19:32:02 +10:00