Erik Johnston c9dbee50ae Fixup pusher pool notifications (#8287) ... `pusher_pool.on_new_notifications` expected a min and max stream ID, however that was not what we were passing in. Instead, let's just pass it the current max stream ID and have it track the last stream ID it got passed. I believe that it mostly worked as we called the function for every event. However, it would break for events that got persisted out of order, i.e, that were persisted but the max stream ID wasn't incremented as not all preceding events had finished persisting, and push for that event would be delayed until another event got pushed to the effected users.		2020-09-09 16:56:08 +01:00
..
streams	Stop sub-classing object (#8249)	2020-09-04 06:54:56 -04:00
__init__.py	Fix some spelling mistakes / typos. (#7811)	2020-07-09 09:52:58 -04:00
client.py	Fixup pusher pool notifications (#8287)	2020-09-09 16:56:08 +01:00
commands.py	Be stricter about JSON that is accepted by Synapse (#8106)	2020-08-19 07:26:03 -04:00
handler.py	Revert "Add experimental support for sharding event persister. (#8170)" (#8242)	2020-09-04 10:19:42 +01:00
protocol.py	Stop sub-classing object (#8249)	2020-09-04 06:54:56 -04:00
redis.py	Handle replication commands synchronously where possible (#7876)	2020-07-27 18:54:43 +01:00
resource.py	Stop sub-classing object (#8249)	2020-09-04 06:54:56 -04:00