Richard van der Hoff ce428a1abe Fix EventsStream raising assertions when it falls behind ... Figuring out how to correctly limit updates from this stream without dropping entries is far more complicated than just counting the number of rows being returned. We need to consider each query separately and, if any one query hits the limit, truncate the results from the others. I think this also fixes some potentially long-standing bugs where events or state changes could get missed if we hit the limit on either query.		2020-04-24 13:59:21 +01:00
..
data_stores	Fix EventsStream raising assertions when it falls behind	2020-04-24 13:59:21 +01:00
engines
schema	Only run one background update at a time	2020-03-31 17:43:58 +01:00
util
__init__.py
_base.py
background_updates.py	Update docstring per review comments	2020-04-03 10:51:32 +01:00
database.py	bg update to clear out duplicate outbound_device_list_pokes (#7193)	2020-04-07 23:06:39 +01:00
keys.py
persist_events.py
prepare_database.py	Only run one background update at a time	2020-03-31 17:43:58 +01:00
presence.py
purge_events.py
push_rule.py
relations.py
roommember.py
state.py
types.py