You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
I changed my setup for using workers a few days ago. Today, after updating to 1.12 (debian repository from matrix.org), my workers are not starting anymore.
Ah, looks like we're not correctly ignoring send_federation config option (which defaults to True) on non-federation sending workers. As a hacky fix you should be able to add send_federation: false to your worker config file
Description
I changed my setup for using workers a few days ago. Today, after updating to 1.12 (debian repository from matrix.org), my workers are not starting anymore.
Example of the log for a synchrotron worker :
/etc/matrix-synapse/worker/synchrotron-1.yaml:
Steps to reproduce
worked with 1.11 and stopped with the update
Version information
selfhosted
{
"python_version": "3.7.3",
"server_version": "1.12.0"
}
apt, matrix.org repository
The text was updated successfully, but these errors were encountered: