| Commit message (Collapse) | Author | Files | Lines |
|
If we try and persist two state events that have the same ancestor we
calculate the wrong current state when persisting those events.
|
|
(But this doesn't implement the same for deleting access tokens or e2e keys.
Also respond to code review.
|
|
|
|
This implements the proposal here https://docs.google.com/document/d/1C-25Gqz3TXy2jIAoeOKxpNtmme0jI4g3yFGqv5GlAAk for deleting multiple devices at once in a single request.
|
|
|
|
|
|
|
|
This makes it tractable to run synapse under pdb.
|
|
- to make it easier to add more config options.
|
|
When we are using a log_config file, reread it on SIGHUP.
|
|
|
|
|
|
|
|
Unfortunately this significantly increases the size of the already-rather-big
FederationHandler, but the code fits more naturally here, and it paves the way
for the tighter integration that I need between handling incoming PDUs and
doing the join dance.
Other than renaming the existing `FederationHandler.on_receive_pdu` to
`_process_received_pdu` to make way for it, this just consists of the move, and
replacing `self.handler` with `self` and `self` with `self.replication_layer`.
|
|
When we receive PDUs via `get_missing_events`, we have already checked their
sigs, so there is no need to do it again.
|
|
This should be functionally identical: it just seeks to improve readability by
reducing indentation.
|