Brendan Abolivier 855af069a4 Fix instantiation of message retention purge jobs ... When figuring out which topological token to start a purge job at, we need to do the following: 1. Figure out a timestamp before which events will be purged 2. Select the first stream ordering after that timestamp 3. Select info about the first event after that stream ordering 4. Build a topological token from that info In some situations (e.g. quiet rooms with a short max_lifetime), there might not be an event after the stream ordering at step 3, therefore we abort the purge with the error `No event found`. To mitigate that, this patch fetches the first event _before_ the stream ordering, instead of after.		2020-01-15 18:56:18 +00:00
..
main	Fix instantiation of message retention purge jobs	2020-01-15 18:56:18 +00:00
state	Split state groups into a separate data store (#6296)	2019-12-20 10:48:24 +00:00
__init__.py	Modify check_database to take a connection rather than a cursor	2020-01-09 18:05:50 +00:00