OpenCloud
/
MatrixSynapse
mirror of https://github.com/matrix-org/synapse
1
0
Fork 0
Code Issues Releases Wiki Activity

deploy: ceab5a4bfa

pull/11367/head
reivilibre 2021-09-10 15:34:00 +00:00
parent 1f4f0ddf26
commit 97bd03789e
4 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
develop/log_contexts.html
View File

@ -191,7 +191,7 @@ and add it to each log record.</p>
<p>Logcontexts are also used for CPU and database accounting, so that we <p>Logcontexts are also used for CPU and database accounting, so that we
can track which requests were responsible for high CPU use or database can track which requests were responsible for high CPU use or database
activity.</p> activity.</p>
<p>The <code>synapse.logging.context</code> module provides a facilities for managing <p>The <code>synapse.logging.context</code> module provides facilities for managing
the current log context (as well as providing the <code>LoggingContextFilter</code> the current log context (as well as providing the <code>LoggingContextFilter</code>
class).</p> class).</p>
<p>Asynchronous functions make the whole thing complicated, so this document describes <p>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 <code>await_something_interesting</code> is a coroutine, some point. Note that <code>await_something_interesting</code> is a coroutine,
which Python implements as a generator function. When Python which Python implements as a generator function. When Python
garbage-collects generator functions, it gives them a chance to garbage-collects generator functions, it gives them a chance to
clean up by making the <code>async</code> (or <code>yield</code>) raise a <code>GeneratorExit</code> clean up by making the <code>await</code> (or <code>yield</code>) raise a <code>GeneratorExit</code>
exception. In our case, that means that the <code>__exit__</code> handler of exception. In our case, that means that the <code>__exit__</code> handler of
<code>PreserveLoggingContext</code> will carefully restore the request context, but <code>PreserveLoggingContext</code> will carefully restore the request context, but
there is now nothing waiting for its return, so the request context is there is now nothing waiting for its return, so the request context is

4
develop/print.html
View File

@ -12151,7 +12151,7 @@ and add it to each log record.</p>
<p>Logcontexts are also used for CPU and database accounting, so that we <p>Logcontexts are also used for CPU and database accounting, so that we
can track which requests were responsible for high CPU use or database can track which requests were responsible for high CPU use or database
activity.</p> activity.</p>
<p>The <code>synapse.logging.context</code> module provides a facilities for managing <p>The <code>synapse.logging.context</code> module provides facilities for managing
the current log context (as well as providing the <code>LoggingContextFilter</code> the current log context (as well as providing the <code>LoggingContextFilter</code>
class).</p> class).</p>
<p>Asynchronous functions make the whole thing complicated, so this document describes <p>Asynchronous functions make the whole thing complicated, so this document describes
@ -12428,7 +12428,7 @@ and the awaitable chain is now orphaned, and will be garbage-collected at
some point. Note that <code>await_something_interesting</code> is a coroutine, some point. Note that <code>await_something_interesting</code> is a coroutine,
which Python implements as a generator function. When Python which Python implements as a generator function. When Python
garbage-collects generator functions, it gives them a chance to garbage-collects generator functions, it gives them a chance to
clean up by making the <code>async</code> (or <code>yield</code>) raise a <code>GeneratorExit</code> clean up by making the <code>await</code> (or <code>yield</code>) raise a <code>GeneratorExit</code>
exception. In our case, that means that the <code>__exit__</code> handler of exception. In our case, that means that the <code>__exit__</code> handler of
<code>PreserveLoggingContext</code> will carefully restore the request context, but <code>PreserveLoggingContext</code> will carefully restore the request context, but
there is now nothing waiting for its return, so the request context is there is now nothing waiting for its return, so the request context is

2
develop/searchindex.js
View File

File diff suppressed because one or more lines are too long

2
develop/searchindex.json
View File

File diff suppressed because one or more lines are too long