Erik Johnston 8f35f8148e Fix bug where a new writer advances their token too quickly (#16473) ... * Fix bug where a new writer advances their token too quickly When starting a new writer (for e.g. persisting events), the `MultiWriterIdGenerator` doesn't have a minimum token for it as there are no rows matching that new writer in the DB. This results in the the first stream ID it acquired being announced as persisted *before* it actually finishes persisting, if another writer gets and persists a subsequent stream ID. This is due to the logic of setting the minimum persisted position to the minimum known position of across all writers, and the new writer starts off not being considered. * Fix sending out POSITIONs when our token advances without update Broke in #14820 * For replication HTTP requests, only wait for minimal position		2023-10-23 16:57:30 +01:00
..
__init__.py	Merge device list replication streams (#14833)	2023-01-17 09:29:58 +00:00
_base.py	Fix bug where a new writer advances their token too quickly (#16473)	2023-10-23 16:57:30 +01:00
events.py	Fix bug where a new writer advances their token too quickly (#16473)	2023-10-23 16:57:30 +01:00
federation.py	Fix bug where a new writer advances their token too quickly (#16473)	2023-10-23 16:57:30 +01:00
partial_state.py	Fix bug where a new writer advances their token too quickly (#16473)	2023-10-23 16:57:30 +01:00