Write a clear restart indicator in logs

Add error code to room creation error

I'm fed up with never being able to find the point a server restarted in the
logs.

SECURITY UPDATE: Prevent unauthorised users from setting state events in a room
when there is no `m.room.power_levels` event in force in the room. (PR #3397)

Discussion around the Matrix Spec change proposal for this change can be
followed at https://github.com/matrix-org/matrix-doc/issues/1304.

Adjust event auth rules when there is no PL event

We need power levels for this test to do what it is supposed to do.

This error code is mentioned in the documentation at https://matrix.org/docs/api/client-server/#!/Room32creation/createRoom

Make it so that, before there is a power-levels event in the room, you need a
power level of at least 50 to send state.

Partially addresses https://github.com/matrix-org/matrix-doc/issues/1192

stop pretending that it returns a boolean, which just almost gave me a heart
attack.

it makes it easier for me to reason about

Fix commandline federation_client to send the right Host header

Use the correct flag (enable_metrics) when warning about an incorrect metrics setup

Use the RegistryProxy for appservices too

Signed-off-by: Travis Ralston <travpc@gmail.com>

Signed-off-by: Travis Ralston <travpc@gmail.com>

This appears to have stopped working since matrix.org moved to cloudflare. The
Host header should match the name of the server, not whatever is in the SRV
record.

Remove email addresses / phone numbers from ID servers when they're removed from synapse

Changes in synapse v0.31.1 (2018-06-08)
=======================================

v0.31.1 fixes a security bug in the ``get_missing_events`` federation API
where event visibility rules were not applied correctly.

We are not aware of it being actively exploited but please upgrade asap.

Bug Fixes:

* Fix event filtering in get_missing_events handler (PR #3371)

Try to log more helpful info when a sig verification fails

Fix event filtering in get_missing_events handler

Firstly, don't swallow the reason for the failure

Secondly, don't assume all exceptions are verification failures

Thirdly, log a bit of info about the key being used if debug is enabled