Per the Client-Server API[0] we should return
`M_NOT_FOUND` if the room isn't found instead
of generic SynapseError.

This ensures that /directory/list API returns
404 for room not found instead of 400.

[0]: https://matrix.org/docs/spec/client_server/unstable.html#get-matrix-client-r0-directory-list-room-roomid



Signed-off-by: Serban Constantin <serban.constantin@gmail.com>

Remove pdu_failures from transactions

Make EventStore inherit from EventFederationStore

Add some documentation for using the dashboard

Only import secrets when available

The field is never read from, and all the opportunities given to populate it are not utilized. It should be very safe to remove this.

secrets got introduced in python 3.6 so this class is not available
in 3.5 and before.

This now checks for the current running version and only tries using
secrets if the version is 3.6 or above

Signed-Off-By: Matthias Kesler <krombel@krombel.de>

make /context lazyload & filter aware.

if inviter_display_name == ""||None then default to inviter MXID

Add instructions for install on OpenSUSE and SLES

Update the send_leave path to be an event_id

Stop populating events.content

* attempt at deduplicating lazy-loaded members

as per the proposal; we can deduplicate redundant lazy-loaded members
which are sent in the same sync sequence. we do this heuristically
rather than requiring the client to somehow tell us which members it
has chosen to cache, by instead caching the last N members sent to
a client, and not sending them again.  For now we hardcode N to 100.
Each cache for a given (user,device) tuple is in turn cached for up to
X minutes (to avoid the caches building up).  For now we hardcode X to 30.

* add include_redundant_members filter option & make it work

* remove stale todo

* add tests for _get_some_state_from_cache

* incorporate review

Remove some redundant joins on event_edges.room_id

It's still not used, however the parameter is an event ID not a transaction ID.

Fix some looping_call calls which were broken in #3604

There's no real point in ever making the column non-nullable, and doing so
breaks the sytests.

This field is no longer read from, so we should stop populating it. Once we're
happy that this doesn't break everything, and a rollback is unlikely, we can
think about dropping the column.

We've long passed the point where it's possible to have the same event_id in
different tables, so these join conditions are redundant: we can just join on
event_id.

event_edges is of non-trivial size, and the room_id column is wasteful, so
let's stop reading from it. In future, we can stop writing to it, and then drop
it.

(since it uses methods therein)

Turns out that we had a bunch of things which were incorrectly importing
EventWorkerStore from events.py rather than events_worker.py, which broke once
I removed the import into events.py.

It turns out that looping_call does check the deferred returned by its
callback, and (at least in the case of client_ips), we were relying on this,
and I broke it in #3604.

Update run_as_background_process to return the deferred, and make sure we
return it to clock.looping_call.

Implement the lazy_load_members room state filter parameter

Fix a minor documentation typo in on_make_leave

 Correctly handle outliers during persist events

Fix another logcontext leak in _persist_events