1
0
Files
synapse/changelog.d
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
..
2020-03-24 11:59:04 +00:00
2020-02-28 11:27:37 +00:00
2020-04-01 12:44:51 +01:00
2020-03-24 10:36:44 +00:00
2020-03-26 20:35:50 +02:00
2020-03-27 12:01:37 +00:00
2020-03-27 12:30:59 +00:00
2020-03-31 15:50:48 +01:00