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	Add room details admin endpoint (#7317)	2020-05-07 15:33:07 -04:00
_base.py	Clarify list/set/dict/tuple comprehensions and enforce via flake8 (#6957)	2020-02-21 07:15:07 -05:00
groups.py	Move admin endpoints into separate files (#6308)	2019-11-20 11:49:11 +00:00
media.py	Fix and add test to deprecated quarantine media admin api (#6756)	2020-01-22 11:05:50 +00:00
purge_room_servlet.py	Remove unnecessary parentheses around return statements (#5931)	2019-08-30 16:28:26 +01:00
rooms.py	Add ability to wait for replication streams (#7542)	2020-05-22 14:21:54 +01:00
server_notice_servlet.py	Port synaps/rest/client/server_notice_servlet.py to async/await	2019-10-11 12:21:40 +01:00
users.py	Hash passwords earlier in the password reset process (#7538)	2020-05-20 09:48:03 -04:00