mirror of
https://mau.dev/maunium/synapse.git
synced 2024-12-17 07:43:51 +01: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. |
||
---|---|---|
.. | ||
databases | ||
util | ||
__init__.py | ||
test__base.py | ||
test_account_data.py | ||
test_appservice.py | ||
test_background_update.py | ||
test_base.py | ||
test_cleanup_extrems.py | ||
test_client_ips.py | ||
test_database.py | ||
test_devices.py | ||
test_directory.py | ||
test_e2e_room_keys.py | ||
test_end_to_end_keys.py | ||
test_event_chain.py | ||
test_event_federation.py | ||
test_event_metrics.py | ||
test_event_push_actions.py | ||
test_events.py | ||
test_id_generators.py | ||
test_main.py | ||
test_monthly_active_users.py | ||
test_profile.py | ||
test_purge.py | ||
test_receipts.py | ||
test_redaction.py | ||
test_registration.py | ||
test_relations.py | ||
test_rollback_worker.py | ||
test_room.py | ||
test_room_search.py | ||
test_roommember.py | ||
test_sliding_sync_tables.py | ||
test_state.py | ||
test_stream.py | ||
test_transactions.py | ||
test_txn_limit.py | ||
test_unsafe_locale.py | ||
test_user_directory.py | ||
test_user_filters.py |