diff options
| author | erikjohnston <erikjohnston@users.noreply.github.com> | 2023-09-26 16:01:35 +0000 |
|---|---|---|
| committer | erikjohnston <erikjohnston@users.noreply.github.com> | 2023-09-26 16:01:35 +0000 |
| commit | 2a48d0838b46963b134b4351d4da0dd352cbd8bf (patch) | |
| tree | 9f615b3044851520d090d8d6839c2c46ab7997ab /latest/log_contexts.html | |
| parent | deploy: ec1c709440d99b0d8042b669e17c899cd6fd8b84 (diff) | |
| download | synapse-2a48d0838b46963b134b4351d4da0dd352cbd8bf.tar.xz | |
deploy: 88ba67eb91215a708f321e16559fe3c2c0d0a407
Diffstat (limited to 'latest/log_contexts.html')
| -rw-r--r-- | latest/log_contexts.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/latest/log_contexts.html b/latest/log_contexts.html index 928a92eca2..75e0533a8b 100644 --- a/latest/log_contexts.html +++ b/latest/log_contexts.html @@ -215,7 +215,7 @@ blocking operation, and returns an awaitable:</p> <p>So we have stopped processing the request (and will probably go on to start processing the next), without clearing the logcontext.</p> <p>To circumvent this problem, synapse code assumes that, wherever you have -an awaitable, you will want to <code>await</code> it. To that end, whereever +an awaitable, you will want to <code>await</code> it. To that end, wherever functions return awaitables, we adopt the following conventions:</p> <p><strong>Rules for functions returning awaitables:</strong></p> <blockquote> |