diff options
author | Richard van der Hoff <1389908+richvdh@users.noreply.github.com> | 2022-01-04 16:36:33 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-01-04 16:36:33 +0000 |
commit | b38bdae3a2e5b7cfe862580368b996b8d7dfa50f (patch) | |
tree | 2ee349524c1fbe9e34ac6439dc5a6ff7ed39a570 /changelog.d | |
parent | `FederationClient.backfill`: stop flagging events as outliers (#11632) (diff) | |
download | synapse-b38bdae3a2e5b7cfe862580368b996b8d7dfa50f.tar.xz |
Fix AssertionErrors after purging events (#11642)
* Fix AssertionErrors after purging events If you purged a bunch of events from your database, and then restarted synapse without receiving more events, then you would get a bunch of AssertionErrors on restart. This fixes the situation by rewinding the stream processors. * `check-newsfragment`: ignore deleted newsfiles
Diffstat (limited to 'changelog.d')
-rw-r--r-- | changelog.d/11536.bugfix | 1 | ||||
-rw-r--r-- | changelog.d/11536.misc | 1 | ||||
-rw-r--r-- | changelog.d/11642.bugfix | 1 |
3 files changed, 2 insertions, 1 deletions
diff --git a/changelog.d/11536.bugfix b/changelog.d/11536.bugfix new file mode 100644 index 0000000000..4a1b007254 --- /dev/null +++ b/changelog.d/11536.bugfix @@ -0,0 +1 @@ +Fix a long-standing bug which could cause `AssertionError`s to be written to the log when Synapse was restarted after purging events from the database. diff --git a/changelog.d/11536.misc b/changelog.d/11536.misc deleted file mode 100644 index b9191c111b..0000000000 --- a/changelog.d/11536.misc +++ /dev/null @@ -1 +0,0 @@ -Improvements to log messages around handling stream ids. diff --git a/changelog.d/11642.bugfix b/changelog.d/11642.bugfix new file mode 100644 index 0000000000..4a1b007254 --- /dev/null +++ b/changelog.d/11642.bugfix @@ -0,0 +1 @@ +Fix a long-standing bug which could cause `AssertionError`s to be written to the log when Synapse was restarted after purging events from the database. |