update synapse 1.56.0 -> 1.57.0

[aine-etke]

no config changes

[spantaleev]

Thanks! 👍

---

This changelog entry for Synapse v1.57 may be important to some users:

Changes to database schema for application services

Synapse v1.57.0 includes a matrix-org/synapse#12209 to the way transaction IDs are managed for application services. If your deployment uses a dedicated worker for application service traffic, it must be stopped when the database is upgraded (which normally happens when the main process is upgraded), to ensure the change is made safely without any risk of reusing transaction IDs.

Deployments which do not use separate worker processes can be upgraded as normal. Similarly, deployments where no applciation services are in use can be upgraded as normal.

[aine-etke]

But the start tag does the full stop

[spantaleev]

It does bring all services to a full stop, and then starts them again.

Various matrix-synapse-worker-*.service services depend on matrix-synapse.service (and sleep 5 seconds), so the main one should be starting before worker processes. Although.. those systemd dependencies and delays are not very reliable, so I suppose some worker could potentially start while matrix-synapse.service is still starting up or is slowly running some migrations.

From what I understand, it's safest if some application service worker only gets to start after matrix-synapse.service has managed to fully complete the migration.

---

Well, let's ignore it and see what happens. 🤞

[aine-etke]

Could you add a notice in the changelog about it?

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.