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
..
main	Fix device list update stream ids going backward (#7158)	2020-04-03 10:40:22 +01:00
state	Clarify list/set/dict/tuple comprehensions and enforce via flake8 (#6957)	2020-02-21 07:15:07 -05:00
__init__.py	Modify check_database to take a connection rather than a cursor	2020-01-09 18:05:50 +00:00