diff options
| author | Richard van der Hoff <richard@matrix.org> | 2020-04-23 18:19:08 +0100 |
|---|---|---|
| committer | Richard van der Hoff <richard@matrix.org> | 2020-04-24 13:59:21 +0100 |
| commit | ce428a1abe6aae25e236baf268f56b1811cba333 (patch) | |
| tree | 17397b3c6a3bb3b6b68fbf1c4f30f971984293c9 /synapse/events | |
| parent | Make it clear that the limit for an update_function is a target (diff) | |
| download | synapse-ce428a1abe6aae25e236baf268f56b1811cba333.tar.xz | |
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.
Diffstat (limited to 'synapse/events')
0 files changed, 0 insertions, 0 deletions