Eric Eastwood e7d98d3429 Remove sentinel logcontext in Clock utilities (looping_call, looping_call_now, call_later) (#18907) ... Part of https://github.com/element-hq/synapse/issues/18905 Lints for ensuring we use `Clock.call_later` instead of `reactor.callLater`, etc are coming in https://github.com/element-hq/synapse/pull/18944 ### Testing strategy 1. Configure Synapse to log at the `DEBUG` level 1. Start Synapse: `poetry run synapse_homeserver --config-path homeserver.yaml` 1. Wait 10 seconds for the [database profiling loop](9cc4001778/synapse/storage/database.py (L711)) to execute 1. Notice the logcontext being used for the `Total database time` log line Before (`sentinel`): ``` 2025-09-10 16:36:58,651 - synapse.storage.TIME - 707 - DEBUG - sentinel - Total database time: 0.646% {room_forgetter_stream_pos(2): 0.131%, reap_monthly_active_users(1): 0.083%, get_device_change_last_converted_pos(1): 0.078%} ``` After (`looping_call`): ``` 2025-09-10 16:36:58,651 - synapse.storage.TIME - 707 - DEBUG - looping_call - Total database time: 0.646% {room_forgetter_stream_pos(2): 0.131%, reap_monthly_active_users(1): 0.083%, get_device_change_last_converted_pos(1): 0.078%} ```		2025-09-22 14:51:13 -05:00
..
__init__.py	Write some tests for the email pusher (#4095)	2018-10-30 23:55:43 +11:00
test_bulk_push_rule_evaluator.py	Introduce Clock.call_when_running(...) to include logcontext by default (#18944)	2025-09-22 10:27:59 -05:00
test_email.py	Remove sentinel logcontext in Clock utilities (looping_call, looping_call_now, call_later) (#18907)	2025-09-22 14:51:13 -05:00
test_http.py	Introduce Clock.call_when_running(...) to include logcontext by default (#18944)	2025-09-22 10:27:59 -05:00
test_presentable_names.py	Correctly mention previous copyright (#16820)	2024-01-23 11:26:48 +00:00
test_push_rule_evaluator.py	Introduce Clock.call_when_running(...) to include logcontext by default (#18944)	2025-09-22 10:27:59 -05:00