zalando / logbook / #5048

98%

master: 100%

push

Use default coroutine context in ktor client (#2087)

It appears that when nestin coroutine contexts via `scope.launch(coroutineContext) {}` LogbookClient may lead to deadlocks on big responses, as `loggingContent.discard()` uses blocking operations underneath and if other plugins interferred with the current coroutine scope.

When inheriting the scope it seems that the issue is resolved, as Dispatchers.IO is used and not kotlinx.coroutines.BlockingEventLoop as the coroutine element.

1 of 1 new or added line in 1 file covered. (100.0%)

3706 of 3706 relevant lines covered (100.0%)

1.0 hits per line