forked from MirrorHub/synapse
b076bc276e
As far as I can tell our logging contexts are meant to log the request ID, or sometimes the request ID followed by a suffix (this is generally stored in the name field of LoggingContext). There's also code to log the name@memory location, but I'm not sure this is ever used. This simplifies the code paths to require every logging context to have a name and use that in logging. For sub-contexts (created via nested_logging_contexts, defer_to_threadpool, Measure) we use the current context's str (which becomes their name or the string "sentinel") and then potentially modify that (e.g. add a suffix). |
||
|---|---|---|
| .. | ||
| caches | ||
| __init__.py | ||
| test_async_utils.py | ||
| test_dict_cache.py | ||
| test_expiring_cache.py | ||
| test_file_consumer.py | ||
| test_itertools.py | ||
| test_linearizer.py | ||
| test_logcontext.py | ||
| test_logformatter.py | ||
| test_lrucache.py | ||
| test_ratelimitutils.py | ||
| test_retryutils.py | ||
| test_rwlock.py | ||
| test_stream_change_cache.py | ||
| test_stringutils.py | ||
| test_threepids.py | ||
| test_treecache.py | ||
| test_wheel_timer.py | ||