5.9 KiB
+++ title = "Synapse 0.33.7 released!" path = "/blog/2018/10/18/synapse-0-33-7-released"
[taxonomies] author = ["Neil Johnson"] category = ["Releases"] +++
Hey ho, let's go. Synapse 0.33.7 has arrived.
Regular readers will know how close we are to a full python 3 release. We are not quite there yet but 0.33.7 has support for Synapse under worker mode and we've running it on matrix.org this week. We need more time to conclusively gauge performance improvements but the Synchrotron workers are running with 33% less RAM. Thanks to everyone who has been running their servers under py3, if you do spot anything unusual just let us know. Once we've been running it a bit longer on matrix.org, we'll cut a 0.34.0 release with a recommendation that one and all upgrade to python 3.
Aside from that this release contains support for server side end to end key backups, paving the way for client side support in Riot and Rich continues his long running federation bug squash-a-thon which should help with a whole host of federation snafus.
Up next on the horizon is returning in earnest to getting the server to server r0 spec out starting with shipping our brand new super shiny state resolution algorithm.
As a final point, for those of you that deploy from git checkout or a snapshot url and have email notifications enabled please take a look warning in the change log.
As a final final point #synapse:matrix.org is now an officially supported room, aimed at Synapse admins. If you've not done so already please do drop by and say Hi.
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.
Onwards!
Synapse 0.33.7 Change Log
Warning: This release removes the example email notification templates from res/templates (they are now internal to the python package). This should only affect you if you (a) deploy your Synapse instance from a git checkout or a github snapshot URL, and (b) have email notifications enabled.
If you have email notifications enabled, you should ensure that email.template_dir is either configured to point at a directory where you have installed customised templates, or leave it unset to use the default templates.
The configuration parser will try to detect the situation where email.template_dir is incorrectly set to res/templates and do the right thing, but will warn about this.
Features
- Ship the example email templates as part of the package (#4052)
- Add support for end-to-end key backup (MSC1687) (#4019)
Bugfixes
- Fix bug which made get_missing_events return too few events (#4045)
- Fix bug in event persistence logic which caused 'NoneType is not iterable' (#3995)
- Fix exception in background metrics collection (#3996)
- Fix exception handling in fetching remote profiles (#3997)
- Fix handling of rejected threepid invites (#3999)
- Workers now start on Python 3. (#4027)
- Synapse now starts on Python 3.7. (#4033)