synapse-product/synapse/replication
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
..
http Remove 'limit' param from get_repl_stream_updates API 2020-04-23 15:44:35 +01:00
slave Move catchup of replication streams to worker. (#7024) 2020-03-25 14:54:01 +00:00
tcp Fix EventsStream raising assertions when it falls behind 2020-04-24 13:59:21 +01:00
__init__.py Add a /replication API for extracting the updates that happened on 2016-03-01 14:49:41 +00:00