I’m seeing some weird behavior where I use a ktor client within a `withContext` block and the reques...

# ktor

[David Glasser]

I’m seeing some weird behavior where I use a ktor client within a withContext block and the request succeeds but the withContext never hangs. like, i have:

<http://log.info|log.info>("going to execute request $callsite")
withContext(MyContextThingy()) {
 <http://log.info|log.info>("in first context")
}
<http://log.info|log.info>("back from context")
val res: HttpResponse = withContext(MyContextThingy()) {
 <http://log.info|log.info>("top of context")
 val response: HttpResponse = httpClient.request {
  url.takeFrom([e-mail])
  method = <http://HttpMethod.Post|HttpMethod.Post>
  contentType(ContentType.Application.Json)
  body = req
 }
 <http://log.info|log.info>("after request")
 response
}
<http://log.info|log.info>("after WC")
res

and it gets in and out of the first withContext fine, and logs after request, but never after WC. anyone seen anything odd like this?

[David Glasser]

this is being run from within ktor-server, if that makes a different

[David Glasser]

i guess withContext does scoping, so maybe my ktor-client is leaking a job?

[David Glasser]

is it because i’m not calling receive() on the response?

[David Glasser]

ah got it. yeah, if we create a response and don’t receive it, you better not try to end a coroutine scope