Lukasz Kalnik

You might want to take a look at a Retrofit adapter for Either (currently in PR): https://github.com/arrow-kt/arrow/pull/2621 It lets you define your API as returning `Unit` in case of success...

Actually there is an even simpler [workaround](https://github.com/square/retrofit/issues/3075#issuecomment-515400245): change the return type of your API call to `Response`: ``` import retrofit2.Response interface WebInterface { @GET("user/revoke") suspend fun logout(): Response } ```...

Thanks for a super fast answer! Yes, that makes sense. We should not break existing apps. What about allowing setting a custom timeout from `DNSSDBindable`? The [DNSSD constructor which allows...

> While we are waiting for a solution, I have written a simple extension. It allows to get the same `testCoroutineScheduler` every time it is accessed during a test: >...

Thanks for the quick response! I can't see it though: Do I need to include some special artifact? I'm on Kotest 5.8.1

Did you mean `TestScopeElement`?

@Mexator when using this extension in my test now I get a weird timeout error: ``` io.kotest.engine.test.interceptors.TestTimeoutException: Test 'screen was just opened' did not complete within 2h 46m 40s ```

Thanks for your suggestions! I really appreciate your help on this. I see the following when debugging coroutines: so only one of them is on the `StandardTestDispatcher`. I test an...

This also happens when I change the test to a `StringSpec`, so there is no nesting (and use `BetterTestSchedulerExtension`). It also happens when I don't set the main dispatcher and...

I think I'm getting closer: I use https://github.com/cashapp/turbine in my test, and when I remove it, the test passes also with `BetterTestSchedulerExtension`. Probably it uses some other dispatcher under the...