Change slave storage to use new replication interface
As the TCP replication uses a slightly different API and streams than the HTTP replication. This breaks HTTP replication.
Showing
- synapse/replication/slave/storage/_base.py 7 additions, 24 deletionssynapse/replication/slave/storage/_base.py
- synapse/replication/slave/storage/account_data.py 18 additions, 31 deletionssynapse/replication/slave/storage/account_data.py
- synapse/replication/slave/storage/deviceinbox.py 10 additions, 13 deletionssynapse/replication/slave/storage/deviceinbox.py
- synapse/replication/slave/storage/devices.py 10 additions, 14 deletionssynapse/replication/slave/storage/devices.py
- synapse/replication/slave/storage/events.py 17 additions, 40 deletionssynapse/replication/slave/storage/events.py
- synapse/replication/slave/storage/presence.py 9 additions, 10 deletionssynapse/replication/slave/storage/presence.py
- synapse/replication/slave/storage/push_rule.py 10 additions, 13 deletionssynapse/replication/slave/storage/push_rule.py
- synapse/replication/slave/storage/pushers.py 6 additions, 10 deletionssynapse/replication/slave/storage/pushers.py
- synapse/replication/slave/storage/receipts.py 13 additions, 11 deletionssynapse/replication/slave/storage/receipts.py
- synapse/replication/slave/storage/room.py 6 additions, 5 deletionssynapse/replication/slave/storage/room.py
- tests/replication/slave/storage/_base.py 22 additions, 8 deletionstests/replication/slave/storage/_base.py
Loading
Please register or sign in to comment