summary refs log tree commit diff
path: root/synapse/util/debug.py (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Remove full_twisted_stacktraces optionErik Johnston2017-01-121-71/+0
| | | | | | | | | | | | | | | | | The debug 'full_twisted_stacktraces' flag caused synapse to rewrite twisted deferreds to always fire the callback on the next reactor tick. This was to force the deferred to always store the stacktraces on exceptions, and thus be more likely to have a full stacktrace when it reaches the final error handlers and gets printed to the logs. Dynamically rewriting things is generally bad, and in particular this change violates assumptions of various bits of Twisted. This wouldn't necessarily be so bad, but it turns out this option has been turned on on some production servers. Turning the option can cause e.g. #1778. For now, lets just entirely nuke this option.
* copyrightsMatthew Hodgson2016-01-071-1/+1
|
* Track the cpu used in the main thread by each logging contextMark Haines2015-12-031-2/+1
|
* Fix pep8 warnings.Mark Haines2015-10-131-8/+12
|
* Bounce all deferreds through the reactor to make debugging easier.Mark Haines2015-10-131-0/+68
If all deferreds wait a reactor tick before resolving then there is always a chance to add an errback to the deferred so that stacktraces get reported, rather than being discarded.