summary refs log tree commit diff
path: root/scripts-dev/tail-synapse.py (unfollow)
Commit message (Collapse)AuthorFilesLines
2017-10-12log when we get an exception handling replication updateshera1-1/+5
2017-10-11logformatter: fix AttributeErrorRichard van der Hoff1-3/+11
make sure we have the relevant fields before we try to log them.
2017-10-11Fix fetching remote summariesErik Johnston1-2/+2
2017-10-11peeeeeeeeep8888888888888888888888888888Erik Johnston1-1/+1
2017-10-11Fix group stream replicationErik Johnston1-7/+7
The stream update functions expect the storage function to return a list of tuples.
2017-10-11Fix stackoverflow and logcontexts from linearizerRichard van der Hoff2-6/+46
1. make it not blow out the stack when there are more than 50 things waiting for a lock. Fixes https://github.com/matrix-org/synapse/issues/2505. 2. Make it not mess up the log contexts.
2017-10-11fix isinstanceDavid Baker1-1/+1
2017-10-11Fix typo in invite to groupErik Johnston1-1/+1
2017-10-11Allow error strings from spam checkerDavid Baker1-2/+6
2017-10-11fix a logcontext leak in read receipt handlingRichard van der Hoff1-0/+4
2017-10-11log pdu_failures from incoming transactionsRichard van der Hoff1-2/+3
... even if we have no EDUs. This appears to have been introduced in 476899295f5fd6cff64799bcbc84cd4bf9005e33.
2017-10-11Fix typoErik Johnston1-1/+1
2017-10-11Fix attestations to check correct server nameErik Johnston1-10/+20
2017-10-11Fix schema delta versionsErik Johnston3-1/+1
2017-10-11Validate room idsErik Johnston1-1/+5
2017-10-10pep8David Baker2-3/+5
2017-10-10Don't KeyError if no power_levels eventDavid Baker1-1/+3
2017-10-10Use notification levels in power_levelsDavid Baker3-12/+22
Rather than making the condition directly require a specific power level. This way the level require to notify a room can be configured per room.
2017-10-10There was already a constant for thisDavid Baker1-3/+4
also update copyright
2017-10-10More optimisationDavid Baker1-6/+9
2017-10-10What year is it!? Who's the president!?David Baker1-1/+1
2017-10-09fed server: process PDUs for different rooms in parallelRichard van der Hoff1-19/+34
With luck, this will give a real-time improvement when there are many rooms and the server ends up calling out to fetch missing events.
2017-10-09Fed server: use a linearizer for ongoing transactionsRichard van der Hoff1-1/+29
We don't want to process the same transaction multiple times concurrently, so use a linearizer.
2017-10-09fed server: refactor on_incoming_transactionRichard van der Hoff1-24/+29
Move as much as possible to after the have_responded check, and reduce the number of times we iterate over the pdu list.
2017-10-09Fed server: Move origin-check code to _handle_received_pduRichard van der Hoff1-24/+24
The response-building code expects there to be an entry in the `results` list for each entry in the pdu_list, so the early `continue` was messing this up. That doesn't really matter, because all that the federation client does is log any errors, but it's pretty poor form.