watcha-synapse

History

Andreas Rammhold e3e73e181b Upsert redactions in case they already exists (#10343 ) * Upsert redactions in case they already exists Occasionally, in combination with retention, redactions aren't deleted from the database whenever they are due for deletion. The server will eventually try to backfill the deleted events and trip over the already existing redaction events. Switching to an UPSERT for those events allows us to recover from there situations. The retention code still needs fixing but that is outside of my current comfort zone on this code base. This is related to #8707 where the error was discussed already. Signed-off-by: Andreas Rammhold <andreas@rammhold.de> * Also purge redactions when purging events Previously redacints where left behind leading to backfilling issues when the server stumbled across the already existing yet to be backfilled redactions. This issues has been discussed in #8707. Signed-off-by: Andreas Rammhold <andreas@rammhold.de>		3 years ago
..
.gitignore	Correct attrs package name in requirements (#3492 )	6 years ago
9721.removal	Remove functionality associated with unused historical stats tables (#9721 )	3 years ago
10250.bugfix	Add base starting insertion event when no chunk ID is provided (MSC2716) (#10250 )	3 years ago
10287.doc	Update links to documentation in sample config (#10287 )	3 years ago
10313.doc	Simplify structure of room admin API docs (#10313 )	3 years ago
10316.misc	Rebuild event auth when rebuilding an event after a call to a `ThirdPartyEventRules` module (#10316 )	3 years ago
10317.bugfix	Ignore EDUs for rooms we're not in (#10317 )	3 years ago
10322.doc	Fix a broken link in the admin api docs (#10322 )	3 years ago
10324.misc	Minor changes to `user_daily_visits` (#10324 )	3 years ago
10337.doc	Fix formatting in the logcontext doc (#10337 )	3 years ago
10343.bugfix	Upsert redactions in case they already exists (#10343 )	3 years ago