Kill off some old python 2 code

this is no longer needed on python 3

this is a no-op under python 3

this is a no-op on python 3.

this is a no-op on python 3.

Make sure that the AccountDataStream presents complete updates, in the right
order.

This is much the same fix as #7337 and #7358, but applied to a different stream.

This is required as both event persistence and the background update needs access to this function. It should be perfectly safe for two workers to write to that table at the same time.

This allows us to have the logic on both master and workers, which is necessary to move event persistence off master.

We also combine the instantiation of ID generators from DataStore and slave stores to the base worker stores. This allows us to select which process writes events independently of the master/worker splits.

also a small clarification to nginx

The specific headers that are passed using this new configuration format
are Host and X-Forwarded-For, which should be all that's required.

Note that for production another matcher should be added in the first
section to properly handle the base_url lookup:
reverse_proxy /.well-known/matrix/* http://localhost:8008



Signed-off-by: Jeff Peeler <jpeeler@gmail.com>

These PRs have gone straight to `master` and aren't really relevant to the
release, so it doesn't make sense to have changelog entries for them.

* general updates to CONTRIBUTING.md
* notes on updating your PR
* Notes on squash-merging or otherwise
* document git branching model

In a new room version, the "notifications" key of power level events are
subject to restricted auth rules.

This is so that the logic can happen on both master and workers when we move event persistence out.

Synapse 1.13.0rc2 (2020-05-14)
==============================

Bugfixes
--------

- Fix a long-standing bug which could cause messages not to be sent over federation, when state events with state keys matching user IDs (such as custom user statuses) were received. ([\#7376](https://github.com/matrix-org/synapse/issues/7376))
- Restore compatibility with non-compliant clients during the user interactive authentication process, fixing a problem introduced in v1.13.0rc1. ([\#7483](https://github.com/matrix-org/synapse/issues/7483))

Internal Changes
----------------

- Fix linting errors in new version of Flake8. ([\#7470](https://github.com/matrix-org/synapse/issues/7470))

Fix a bug where the `get_joined_users` cache could be corrupted by custom
status events (or other state events with a state_key matching the user ID).

The bug was introduced by #2229, but has largely gone unnoticed since then.

Fixes #7099, #7373.

This backs out some of the validation for the client dictionary and logs if
this changes during a user interactive authentication session instead.

This is safe as we can now write to cache invalidation stream on workers, and is required for when we move event persistence off master.

Signed-off-by: Paul Tötterman <paul.totterman@iki.fi>