| Commit message (Collapse) | Author | Files | Lines |
|
Apparently the github RST renderer doesn't like Note blocks.
|
|
|
|
Fix a bug in ``logcontext.preserve_fn`` which made it leak context into the
reactor, and add a test for it.
Also, get rid of ``logcontext.reset_context_after_deferred``, which tried to do
the same thing but had its own, different, set of bugs.
|
|
This fixes a class of 'Unexpected logcontext' messages, which were happening
because the logcontext was somewhat arbitrarily swapping between the sentinel
and the `run` logcontext.
|
|
background_updates was using `call_later` in a way that leaked the logcontext
into the reactor.
We could have rewritten it to do it properly, but given that we weren't using
the fancier facilities provided by `call_later`, we might as well just use
`async.sleep`, which does the logcontext stuff properly.
|
|
|
|
When we get a rejected event, give it the same state_group as its prev_event,
rather than no state_group at all.
This should fix https://github.com/matrix-org/synapse/issues/1935.
|
|
A few non-functional changes:
* A bunch of docstrings to document types
* Split `EventsStore._persist_events_txn` up a bit. Hopefully it's a bit more
readable.
* Rephrase `EventFederationStore._update_min_depth_for_room_txn` to avoid
mind-bending conditional.
* Rephrase rejected/outlier conditional in `_update_outliers_txn` to avoid
mind-bending conditional.
|
|
|
|
|
|
|
|
|
|
This just takes the existing `room_queues` logic and moves it out to
`on_receive_pdu` instead of `_process_received_pdu`, which ensures that we
don't start trying to fetch prev_events and whathaveyou until the join has
completed.
|
|
|
|
last_user_sync_ts
|
|
|
|
|
|
|
|
|
|
|
|
|
|
... and update some docstrings to correctly reflect the types being used.
get_new_device_msgs_for_remote can return a long under some circumstances,
which was being stored in last_device_list_stream_id_by_dest, and was then
upsetting things on the next loop.
|
|
|
|
to correctly reset the context when we fire off a deferred we aren't going to
wait for.
|
|
|
|
- don't blindly proxy all HTTPRequestExceptions
- log unexpected exceptions at error
- avoid `isinstance`
- improve docs on `from_http_response_exception`
|
|
Give CodeMessageException back its `msg` attribute, and use that to hold the
HTTP status message for HttpResponseException.
|
|
|
|
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.
|
|
Only offer msisdn flows if the x_show_msisdn option is given.
|
|
Changes from https://github.com/matrix-org/synapse/pull/1971
|
|
|
|
This implements the proposal here https://docs.google.com/document/d/1C-25Gqz3TXy2jIAoeOKxpNtmme0jI4g3yFGqv5GlAAk for deleting multiple devices at once in a single request.
|
|
When we proxy a media request to a remote server, add a query-param, which will
tell the remote server to 404 if it doesn't recognise the server_name.
This should fix a routing loop where the server keeps forwarding back to
itself.
Also improves the error handling on remote media fetches, so that we don't
always return a rather obscure 502.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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
r |