Richard van der Hoff daa1ac89a0 Fix device list update stream ids going backward (#7158) ... 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.		2020-04-03 10:40:22 +01:00
..
transport	privacy by default for room dir (#6355)	2019-12-04 09:46:16 +00:00
__init__.py
test_complexity.py	Remove spurious "name" parameter to default_config	2020-03-24 18:33:49 +00:00
test_federation_sender.py	Fix device list update stream ids going backward (#7158)	2020-04-03 10:40:22 +01:00
test_federation_server.py	Clarify list/set/dict/tuple comprehensions and enforce via flake8 (#6957)	2020-02-21 07:15:07 -05:00