summary refs log tree commit diff
path: root/stubs (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Remove redundant "coding: utf-8" lines (#9786)Jonathan de Jong2021-04-142-2/+0
| | | | | | | Part of #9744 Removes all redundant `# -*- coding: utf-8 -*-` lines from files, as python 3 automatically reads source code as utf-8 now. `Signed-off-by: Jonathan de Jong <jonathan@automatia.nl>`
* Fix remaining mypy issues due to Twisted upgrade. (#9608)Patrick Cloke2021-03-151-1/+1
|
* Add logging for redis connection setup (#9590)Richard van der Hoff2021-03-111-1/+3
|
* Update black, and run auto formatting over the codebase (#9381)Eric Eastwood2021-02-162-5/+19
| | | | | | | - 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
* Precompute joined hosts and store in Redis (#9198)Erik Johnston2021-01-261-1/+11
|
* Periodically send pings to detect dead Redis connections (#9218)Erik Johnston2021-01-261-4/+8
| | | | | | | | 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).
* Add an admin API for shadow-banning users. (#9209)Patrick Cloke2021-01-251-1/+0
| | | | | | | | | | 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.
* Run the linters on a consistent list of files (#9038)Richard van der Hoff2021-01-083-14/+5
| | | | | We were running some linters on some files and some on others. Extract a common setting and use it everywhere.
* Enable mypy for synapse.util.caches (#8547)Richard van der Hoff2020-10-152-6/+182
| | | This seemed to entail dragging in a type stub for SortedList.
* Add unit test for event persister sharding (#8433)Erik Johnston2020-10-021-1/+19
|
* Add type hints for state. (#8140)Patrick Cloke2020-08-241-0/+47
|
* Track command processing as a background process (#7879)Richard van der Hoff2020-07-221-0/+1
| | | | I'm going to be doing more stuff synchronously, and I don't want to lose the CPU metrics down the sofa.
* Fix redis password support. (#7401)Erik Johnston2020-05-041-0/+3
| | | | | We forgot to set the password on the subscriber connection, as well as not calling super methods for overridden connectionMade/connectionLost functions.
* Extend StreamChangeCache to support multiple entities per stream ID (#7303)Richard van der Hoff2020-04-222-0/+137
| | | | | | | | | | | | | | | | | | | 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
* Add ability to run replication protocol over redis. (#7040)Erik Johnston2020-04-221-0/+40
This is configured via the `redis` config options.