mirror of
https://mau.dev/maunium/synapse.git
synced 2024-09-28 04:06:00 +00:00
26f81fb5be
Fix outlier re-persisting causing problems with sliding sync tables Follow-up to https://github.com/element-hq/synapse/pull/17512 When running on `matrix.org`, we discovered that a remote invite is first persisted as an `outlier` and then re-persisted again where it is de-outliered. The first the time, the `outlier` is persisted with one `stream_ordering` but when persisted again and de-outliered, it is assigned a different `stream_ordering` that won't end up being used. Since we call `_calculate_sliding_sync_table_changes()` before `_update_outliers_txn()` which fixes this discrepancy (always use the `stream_ordering` from the first time it was persisted), we're working with an unreliable `stream_ordering` value that will possibly be unused and not make it into the `events` table. |
||
|---|---|---|
| .. | ||
| auth | ||
| __init__.py | ||
| auth_blocking.py | ||
| constants.py | ||
| errors.py | ||
| filtering.py | ||
| presence.py | ||
| ratelimiting.py | ||
| room_versions.py | ||
| urls.py | ||