- Mar 15, 2021
-
-
Patrick Cloke authored
-
- Mar 11, 2021
-
-
Richard van der Hoff authored
-
- Feb 16, 2021
-
-
Eric Eastwood authored
- Update black version to the latest - Run black auto formatting over the codebase - Run autoformatting according to [`docs/code_style.md `](https://github.com/matrix-org/synapse/blob/80d6dc9783aa80886a133756028984dbf8920168/docs/code_style.md) - Update `code_style.md` docs around installing black to use the correct version
-
- Jan 26, 2021
-
-
Erik Johnston authored
-
Erik Johnston authored
This is done by creating a custom `RedisFactory` subclass that periodically pings all connections in its pool. We also ensure that the `replyTimeout` param is non-null, so that we timeout waiting for the reply to those pings (and thus triggering a reconnect).
-
- Jan 25, 2021
-
-
Patrick Cloke authored
This expands the current shadow-banning feature to be usable via the admin API and adds documentation for it. A shadow-banned users receives successful responses to their client-server API requests, but the events are not propagated into rooms. Shadow-banning a user should be used as a tool of last resort and may lead to confusing or broken behaviour for the client.
-
- Jan 08, 2021
-
-
Richard van der Hoff authored
We were running some linters on some files and some on others. Extract a common setting and use it everywhere.
-
- Oct 15, 2020
-
-
Richard van der Hoff authored
This seemed to entail dragging in a type stub for SortedList.
-
- Oct 02, 2020
-
-
Erik Johnston authored
-
- Aug 24, 2020
-
-
Patrick Cloke authored
-
- Jul 21, 2020
-
-
Richard van der Hoff authored
I'm going to be doing more stuff synchronously, and I don't want to lose the CPU metrics down the sofa.
-
- May 04, 2020
-
-
Erik Johnston authored
We forgot to set the password on the subscriber connection, as well as not calling super methods for overridden connectionMade/connectionLost functions.
-
- Apr 22, 2020
-
-
Richard van der Hoff authored
First some background: StreamChangeCache is used to keep track of what "entities" have changed since a given stream ID. So for example, we might use it to keep track of when the last to-device message for a given user was received [1], and hence whether we need to pull any to-device messages from the database on a sync [2]. Now, it turns out that StreamChangeCache didn't support more than one thing being changed at a given stream_id (this was part of the problem with #7206). However, it's entirely valid to send to-device messages to more than one user at a time. As it turns out, this did in fact work, because *some* methods of StreamChangeCache coped ok with having multiple things changing on the same stream ID, and it seems we never actually use the methods which don't work on the stream change caches where we allow multiple changes at the same stream ID. But that feels horribly fragile, hence: let's update StreamChangeCache to properly support this, and add some typing and some more tests while we're at it. [1]: https://github.com/matrix-org/synapse/blob/release-v1.12.3/synapse/storage/data_stores/main/deviceinbox.py#L301 [2]: https://github.com/matrix-org/synapse/blob/release-v1.12.3/synapse/storage/data_stores/main/deviceinbox.py#L47-L51
-
Erik Johnston authored
This is configured via the `redis` config options.
-