I’m trying to reimplement an interceptor close to ResponseObserver in my logging feature but half the things it uses are internal 😞

Ok so it looks like it only happens on one of the endpoints I use, this endpoint’s response body is just

OK

. Maybe there’s a race condition that usually allows to log the body before the request’s scope/context disappears because it already takes time to read/deserialize it? And in this case as it’s just

OK

and I ignore the response (I’m doing a

get<Unit>

) the request is ended before the logging ends? I just don’t really know how all of this works, but would that make sense @e5l?

Well yeah just a more clear message would help, I’ll open an issue

I changed

get<Unit>

to

get<String>

and there are no more errors 👍