From 2a48d0838b46963b134b4351d4da0dd352cbd8bf Mon Sep 17 00:00:00 2001 From: erikjohnston Date: Tue, 26 Sep 2023 16:01:35 +0000 Subject: deploy: 88ba67eb91215a708f321e16559fe3c2c0d0a407 --- latest/log_contexts.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'latest/log_contexts.html') 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:

So we have stopped processing the request (and will probably go on to start processing the next), without clearing the logcontext.

To circumvent this problem, synapse code assumes that, wherever you have -an awaitable, you will want to await it. To that end, whereever +an awaitable, you will want to await it. To that end, wherever functions return awaitables, we adopt the following conventions:

Rules for functions returning awaitables:

-- cgit 1.5.1