summary refs log tree commit diff
path: root/tests/server_notices (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Leave out optional keys from /sync (#9919)" (#9940)Erik Johnston2021-05-061-5/+3
| | | This reverts commit e9eb3549d32a6f93d07de8dbd5e1ebe54c8d8278.
* Leave out optional keys from /sync (#9919)DeepBlueV7.X2021-05-051-3/+5
| | | | | | This leaves out all optional keys from /sync. This should be fine for all clients tested against conduit already, but it may break some clients, as such we should check, that at least most of them don't break horribly and maybe back out some of the individual changes. (We can probably always leave out groups for example, while the others may cause more issues.) Signed-off-by: Nicolas Werner <nicolas.werner@hotmail.de>
* 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>`
* Use mock from the stdlib. (#9772)Patrick Cloke2021-04-091-1/+1
|
* Update black, and run auto formatting over the codebase (#9381)Eric Eastwood2021-02-161-1/+5
| | | | | | | - 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
* Remove spurious "SynapseRequest" result from `make_request"Richard van der Hoff2020-12-152-8/+6
| | | | This was never used, so let's get rid of it.
* Remove redundant `HomeserverTestCase.render`Richard van der Hoff2020-11-162-6/+0
|
* Allow for make_awaitable's return value to be re-used. (#8261)Patrick Cloke2020-09-081-9/+5
|
* Convert stats and related calls to async/await (#8192)Patrick Cloke2020-08-271-4/+6
|
* Convert events worker database to async/await. (#8071)Patrick Cloke2020-08-181-3/+3
|
* Convert tags and metrics databases to async/await (#8062)Patrick Cloke2020-08-111-1/+4
|
* Convert synapse.api to async/await (#8031)Patrick Cloke2020-08-061-1/+1
|
* Convert streams to async. (#8014)Patrick Cloke2020-08-041-1/+1
|
* Optimise some references to hs.config (#7546)Richard van der Hoff2020-05-221-27/+33
| | | These are surprisingly expensive, and we only really need to do them at startup.
* Convert synapse.server_notices to async/await. (#7394)Patrick Cloke2020-05-011-1/+1
|
* async/await is_server_admin (#7363)Andrew Morgan2020-05-011-24/+24
|
* Server notices: Dissociate room creation/lookup from invite (#7199)Brendan Abolivier2020-04-041-12/+108
| | | | | | | | | Fixes #6815 Before figuring out whether we should alert a user on MAU, we call get_notice_room_for_user to get some info on the existing server notices room for this user. This function, if the room doesn't exist, creates it and invites the user in it. This means that, if we decide later that no server notice is needed, the user gets invited in a room with no message in it. This happens at every restart of the server, since the room ID returned by get_notice_room_for_user is cached. This PR fixes that by moving the inviting bit to a dedicated function, that's only called when the server actually needs to send a notice to the user. A potential issue with this approach is that the room that's created by get_notice_room_for_user doesn't match how that same function looks for an existing room (i.e. it creates a room that doesn't have an invite or a join for the current user in it, so it could lead to a new room being created each time a user syncs), but I'm not sure this is a problem given it's cached until the server restarts, so that function won't run very often. It also renames get_notice_room_for_user into get_or_create_notice_room_for_user to make what it does clearer.
* Remove spurious "name" parameter to `default_config`Richard van der Hoff2020-03-241-1/+1
| | | | | this is never set to anything other than "test", and is a source of unnecessary boilerplate.
* Option to suppress resource exceeded alerting (#6173)Neil Johnson2019-10-241-2/+57
| | | | The expected use case is to suppress MAU limiting on small instances
* Remove non-functional 'expire_access_token' setting (#5782)Richard van der Hoff2019-07-301-1/+1
| | | | | | | | The `expire_access_token` didn't do what it sounded like it should do. What it actually did was make Synapse enforce the 'time' caveat on macaroons used as access tokens, but since our access token macaroons never contained such a caveat, it was always a no-op. (The code to add 'time' caveats was removed back in v0.18.5, in #1656)
* Run Black. (#5482)Amber Brown2019-06-201-2/+2
|
* Migrate all tests to use the dict-based config format instead of hanging ↵Amber Brown2019-05-132-13/+28
| | | | items off HomeserverConfig (#5171)
* Run Black on the tests again (#5170)Amber Brown2019-05-101-1/+0
|
* Add admin api for sending server_notices (#5121)Richard van der Hoff2019-05-021-1/+1
|
* Move admin api impl to its own packageRichard van der Hoff2019-05-011-3/+3
| | | | It doesn't really belong under rest/client/v1 any more.
* Some more porting to HomeserverTestCase and remove old RESTHelper (#4913)Amber Brown2019-03-221-39/+53
|
* Fix resource limits testsRichard van der Hoff2019-03-191-2/+5
| | | | | Make sure that we have a `server_notices_mxid` set, given that we are relying on it.
* fix broken testRichard van der Hoff2018-10-251-9/+1
| | | | This test stubbed out some stuff in a very weird way. I have no idea why. It broke.
* Fix userconsent on Python 3 (#3938)Amber Brown2018-10-021-0/+100
|
* Port tests/ to Python 3 (#3808)Amber Brown2018-09-071-18/+12
|
* Merge branch 'develop' of github.com:matrix-org/synapse into erikj/admin_contactErik Johnston2018-08-241-0/+1
|\
| * Fix checking if service notice room is already taggedErik Johnston2018-08-241-0/+1
| | | | | | | | This manifested in synapse repeatedly setting the tag for the room
* | Change admin_uri to admin_contact in config and errorsErik Johnston2018-08-241-2/+2
|/
* Fix bug where we resent "limit exceeded" server noticesErik Johnston2018-08-231-0/+66
| | | | This was due to a bug where we mutated a cached event's contents
* Actually run the testsErik Johnston2018-08-231-0/+0
|
* Update notice formatErik Johnston2018-08-221-3/+9
|
* clean up, no functional changesNeil Johnson2018-08-171-15/+17
|
* refactor for readability, and reuse caching for setting tagsNeil Johnson2018-08-161-0/+1
|
* check for room state before deciding on actionNeil Johnson2018-08-161-20/+32
|
* implementation of server notices to alert on hitting resource limitsNeil Johnson2018-08-101-0/+125