From 7a927aac59bad94111ef585dc9770bfc92280e6d Mon Sep 17 00:00:00 2001 From: DMRobertson Date: Tue, 21 Sep 2021 13:05:07 +0000 Subject: deploy: 9ffa787eb243c98a6ca1ecd9eac4a6b5dac2bef0 --- latest/log_contexts.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'latest/log_contexts.html') diff --git a/latest/log_contexts.html b/latest/log_contexts.html index c2fc405736..06e84de758 100644 --- a/latest/log_contexts.html +++ b/latest/log_contexts.html @@ -99,7 +99,7 @@ @@ -191,7 +191,7 @@ and add it to each log record.

Logcontexts are also used for CPU and database accounting, so that we can track which requests were responsible for high CPU use or database activity.

-

The synapse.logging.context module provides a facilities for managing +

The synapse.logging.context module provides facilities for managing the current log context (as well as providing the LoggingContextFilter class).

Asynchronous functions make the whole thing complicated, so this document describes @@ -468,7 +468,7 @@ and the awaitable chain is now orphaned, and will be garbage-collected at some point. Note that await_something_interesting is a coroutine, which Python implements as a generator function. When Python garbage-collects generator functions, it gives them a chance to -clean up by making the async (or yield) raise a GeneratorExit +clean up by making the await (or yield) raise a GeneratorExit exception. In our case, that means that the __exit__ handler of PreserveLoggingContext will carefully restore the request context, but there is now nothing waiting for its return, so the request context is -- cgit 1.4.1