I cracked, and added some type definitions in synapse.storage.

When we get an invite over federation, store the room version in the rooms table.

The general idea here is that, when we pull the invite out again, we'll want to know what room_version it belongs to (so that we can later redact it if need be). So we need to store it somewhere...

Signed-off-by: Uday Bansal <43824981+udaybansal19@users.noreply.github.com>

Ensure 'deactivated' parameter is a boolean on user admin API, Fix error handling of call to deactivate user (#6990)

Some of the database deltas rely on `config.server_name` being set correctly,
so we should check that it is before running the deltas.

Fixes #6870.

Some of the database deltas rely on `config.server_name` being set correctly,
so we should check that it is before running the deltas.

Fixes #6870.

I made a mistake in https://github.com/matrix-org/synapse/pull/6921 - the quotes break the postgres container's startup script (or docker-compose), which makes initdb fail: https://github.com/matrix-org/synapse/pull/6921#issuecomment-590657154



Signed-off-by: Fridtjof Mund <fridtjof@das-labor.org>

`_process_received_pdu` is only called by `on_receive_pdu`, which ignores any
events for unknown rooms, so this is redundant.

This is intended as a precursor to storing room versions when we receive an
invite over federation, but has the happy side-effect of fixing #3374 at last.

In short: change the store_room with try/except to a proper upsert which
updates the right columns.

 * Give `notif_template_html`, `notif_template_text` default values (fixes #6960)
 * Don't complain if `smtp_host` and `smtp_port` are unset, since they have sensible defaults (fixes #6961)
 * Set the example for `enable_notifs` to `True`, for consistency and because it's more useful
 * Raise errors as ConfigError rather than RuntimeError for nicer formatting

Ensure good comprehension hygiene using flake8-comprehensions.

Increase MAX_EVENTS_BEHIND for replication clients

Some small fixes to the copy in #6907.

Stop emitting room alias update events during room creation/upgrade.

Signed-off-by: Ruben Barkow-Kuder <github@r.z11.de>

This may make gc go a bit faster as the gc will know things like
caches/data stores etc. are frozen without having to check.

The state res v2 algorithm only cares about the difference between auth
chains, so we can pass in the known common state to the `get_auth_chain`
storage function so that it can ignore those events.

Make room alias lists peekable

Clean up and update federation docs

it's not in the spec yet, so needs to be unstable. Also add a feature flag for it. Also add a test for admin users.

we have hundreds of path_regexes (see #5118), so let's not convert the same
bytes to str for each of them.

* Increase DB/CPU perf of `_is_server_still_joined` check.

For rooms with large amount of state a single user leaving could cause
us to go and load a lot of membership events and then pull out
membership state in a large number of batches.

* Newsfile

* Update synapse/storage/persist_events.py

Co-Authored-By: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>

* Fix adding if too soon

* Update docstring

* Review comments

* Woops typo

Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>

Fix log in message retention purge jobs

Co-Authored-By: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>