Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Commit

Permalink
Fix 2 typos in docs/log_contexts.md (#10795)
Browse files Browse the repository at this point in the history
  • Loading branch information
reivilibre authored Sep 10, 2021
1 parent 63f28e4 commit ceab5a4
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 2 deletions.
1 change: 1 addition & 0 deletions changelog.d/10795.doc
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Correct 2 typographical errors in the *Log Contexts* documentation.
4 changes: 2 additions & 2 deletions docs/log_contexts.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ 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).

Expand Down Expand Up @@ -351,7 +351,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
Expand Down

0 comments on commit ceab5a4

Please sign in to comment.