Synapse 0.33.9 is here!
Well here you are then, the 9th episode in the Synapse 0.33.x series.
Features wise, 0.33.9 contains a change to the way that GDPR consent works under the hood. It is now plumbed in to the login flow (rather than following immediately afterwards) such that it does not inadvertently break on-boarding. This is part of a broader set of changes that span Synapse and Riot to improve initial first impressions of using matrix.
Separately we now have support for room version upgrades which is pre-requisite for rolling out the new state resolution algorithm, come and join us in #teststateresv2:jki.re if you would like to help us test.
Finally we've spent a bunch of time further improving perf especially in and around reducing device ids federation traffic.
I know I say it every time, but full python 3 support is really really close now, matrix.org is now running entirely on py3 and seeing some amazing perf improvements - the remaining blocker is getting py3 deb packages ready and then we'll ship an official python 3 release. There will also be a blog post to explain what we've been up to and what to expect perf wise.
As ever, you can get the new update here or any of the sources mentioned at https://github.com/matrix-org/synapse. Note, Synapse is now available from PyPI, pick it up here. Also, check out our new Synapse installation guide page.
Synapse 0.33.9 changelog
- Include flags to optionally add
m.login.termsto the registration flow when consent tracking is enabled. (#4004, #4133, #4142, #4184)
- Support for replacing rooms with new ones (#4091, #4099, #4100, #4101)
- Fix exceptions when using the email mailer on Python 3. (#4095)
- Fix e2e key backup with more than 9 backup versions (#4113)
- Searches that request profile info now no longer fail with a 500. (#4122)
- fix return code of empty key backups (#4123)
- If the typing stream ID goes backwards (as on a worker when the master restarts), the worker's typing handler will no longer erroneously report rooms containing new typing events. (#4127)
- Fix table lock of device_lists_remote_cache which could freeze the application (#4132)
- Fix exception when using state res v2 algorithm (#4135)
- Generating the user consent URI no longer fails on Python 3. (#4140, #4163)
- Loading URL previews from the DB cache on Postgres will no longer cause Unicode type errors when responding to the request, and URL previews will no longer fail if the remote server returns a Content-Type header with the chartype in quotes. (#4157)
- The hash_password script now works on Python 3. (#4161)
- Fix noop checks when updating device keys, reducing spurious device list update notifications. (#4164)
Deprecations and Removals
- The disused and un-specced identicon generator has been removed. (#4106)
- The obsolete and non-functional /pull federation endpoint has been removed. (#4118)
- The deprecated v1 key exchange endpoints have been removed. (#4119)
- Synapse will no longer fetch keys using the fallback deprecated v1 key exchange method and will now always use v2. (#4120)
- Fix build of Docker image with docker-compose (#3778)
- Delete unreferenced state groups during history purge (#4006)
- The "Received rdata" log messages on workers is now logged at DEBUG, not INFO. (#4108)
- Reduce replication traffic for device lists (#4109)
synapse_replication_tcp_protocol_*_commandsmetric label to be full command name, rather than just the first character (#4110)
- Log some bits about room creation (#4121)
toxfailure on old systems (#4124)
- Add STATE_V2_TEST room version (#4128)
- Clean up event accesses and tests (#4137)
- The default logging config will now set an explicit log file encoding of UTF-8. (#4138)
- Add helpers functions for getting prev and auth events of an event (#4139)
- Add some tests for the HTTP pusher. (#4149)
- add purge_history.sh and purge_remote_media.sh scripts to contrib/ (#4155)
- HTTP tests have been refactored to contain less boilerplate. (#4156)
- Drop incoming events from federation for unknown rooms (#4165)