- Apr 07, 2017
-
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
fix typo in synctl help
-
Erik Johnston authored
Don't double encode replication data
-
- Apr 06, 2017
-
-
Kim Brose authored
-
Erik Johnston authored
-
Erik Johnston authored
Reduce rate of USER_SYNC repl commands
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
- Apr 05, 2017
-
-
Erik Johnston authored
-
Erik Johnston authored
Rearrange TCP replication metrics
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
Move to using TCP replication
-
Erik Johnston authored
Deduplicate new deviceinbox rows for replication
-
- Apr 04, 2017
-
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
Advance replication streams even if nothing is listening
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
Otherwise the streams don't advance and steadily fall behind, so when a worker does connect either a) they'll be streamed lots of old updates or b) the connection will fail as the streams are too far behind.
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
Replace HTTP replication with TCP replication (Server side part)
-
Erik Johnston authored
-
- Apr 03, 2017
-
-
Richard van der Hoff authored
Cull spurious PreserveLoggingContexts
-
Richard van der Hoff authored
-
Richard van der Hoff authored
Accept join events from all servers
-
Richard van der Hoff authored
Make sure that we accept join events from any server, rather than just the origin server, to make the federation join dance work correctly. (Fixes #1893).
-
Richard van der Hoff authored
In `MessageHandler`, remove `yield` on call to `Notifier.on_new_room_event`: it doesn't return anything anyway.
-
Richard van der Hoff authored
Remove `PreserveLoggingContext` around calls to `Notifier.on_new_room_event`; there is no problem if the logcontext is set when calling it.
-
Richard van der Hoff authored
In `on_new_room_event`, remove `PreserveLoggingContext` - we can call its subroutines with the logcontext set.
-
Richard van der Hoff authored
In `Notifier._on_new_room_event`, `preserve_fn` around its subroutines which return deferreds, so that it is safe to call it with an active logcontext.
-