Jesse Wilson

The Okio watchdog is an process-wide singleton and there's no place to configure it.

@davidfrickert these are daemon threads. They shouldn't keep your process alive on their own.

Fix will be to exit on interrupt, then launch a new thread if new work is enqueued.

Yeah I think your message is good but your delivery is needlessly condescending. It means my first instinct is to close & block. Point taken that this isn't a limitation...

Yeah sorry about this. We're using gradle everywhere which papers over this problem. Will look into building a better story for Maven users.

I’m gonna try doing this on both OkHttp and Okio https://github.com/square/okhttp/pull/7354 https://github.com/square/okio/pull/1125

Worth surveying the field to see what‘s new in the JDK, Firefox, Chrome, etc.

Definitely runBlocking is wrong here. If you want to use coroutines in the call to `proceed()` I think you're in for a bad time.

This post gets into it. https://www.billjings.com/posts/title/foot-marksmanship-with-runblocking/ Coroutines are cooperative multitasking. Running a blocking call or runBlocking inside a coroutine is uncooperative and bad non-local things can happen.

@yschimke with 5.0 we'll ship a tiny subset of our API as multiplatform, and expand coverage in subsequent releases. As long as we don't introduce new APIs we're unlikely to...