Richard van der Hoff c7273c11bc Give pushers their own background logcontext ... Each pusher has its own loop which runs for as long as it has work to do. This should run in its own background thread with its own logcontext, as other similar loops elsewhere in the system do - which means that CPU usage is consistently attributed to that loop, rather than to whatever request happened to start the loop.		2018-10-22 16:12:11 +01:00
..
__init__.py	Remove code that's now been obsoleted or moved elsewhere	2016-04-07 16:31:38 +01:00
action_generator.py	run isort	2018-07-09 16:09:20 +10:00
baserules.py	run isort	2018-07-09 16:09:20 +10:00
bulk_push_rule_evaluator.py	Rename async to async_helpers because async is a keyword on Python 3.7 (#3678)	2018-08-10 23:50:21 +10:00
clientformat.py	run isort	2018-07-09 16:09:20 +10:00
emailpusher.py	Give pushers their own background logcontext	2018-10-22 16:12:11 +01:00
httppusher.py	Give pushers their own background logcontext	2018-10-22 16:12:11 +01:00
mailer.py	Calculate absolute path for email templates	2018-10-19 14:01:59 +01:00
presentable_names.py	run isort	2018-07-09 16:09:20 +10:00
push_rule_evaluator.py	run isort	2018-07-09 16:09:20 +10:00
push_tools.py	run isort	2018-07-09 16:09:20 +10:00
pusher.py	run isort	2018-07-09 16:09:20 +10:00
pusherpool.py	move get_all_pushers call down	2018-10-22 16:12:11 +01:00
rulekinds.py	copyrights	2016-01-07 04:26:29 +00:00