matrix/thirdparty/synapse.git - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Fix device list update stream ids going backward (#7158)	Richard van der Hoff	2020-04-03	1	-0/+6
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Occasionally we could get a federation device list update transaction which looked like: ``` [ {'edu_type': 'm.device_list_update', 'content': {'user_id': '@user:test', 'device_id': 'D2', 'prev_id': [], 'stream_id': 12, 'deleted': True}}, {'edu_type': 'm.device_list_update', 'content': {'user_id': '@user:test', 'device_id': 'D1', 'prev_id': [12], 'stream_id': 11, 'deleted': True}}, {'edu_type': 'm.device_list_update', 'content': {'user_id': '@user:test', 'device_id': 'D3', 'prev_id': [11], 'stream_id': 13, 'deleted': True}} ] ``` Having `stream_ids` which are lower than `prev_ids` looks odd. It might work (I'm not actually sure), but in any case it doesn't seem like a reasonable thing to expect other implementations to support.
*	Rewrite prune_old_outbound_device_pokes for efficiency (#7159)	Richard van der Hoff	2020-03-30	1	-0/+92
\| \| \| \|	make sure we clear out all but one update for the user
*	Add tests for outbound device pokes	Richard van der Hoff	2020-03-27	1	-3/+300
\|
*	Implementation of MSC2314 (#6176)	Amber Brown	2019-11-28	1	-1/+3
\|
*	Run Black. (#5482)	Amber Brown	2019-06-20	1	-24/+24
\|
*	Run Black on the tests again (#5170)	Amber Brown	2019-05-10	1	-47/+66
\|
*	Batch up outgoing read-receipts to reduce federation traffic. (#4890)	Richard van der Hoff	2019-03-20	1	-0/+128
	Rate-limit outgoing read-receipts as per #4730.