Just bumped to Kotlin

1.7.0

and am seeing this in Kotest:

Found interface kotlin.time.TimeMark, but class was expected
java.lang.IncompatibleClassChangeError: Found interface kotlin.time.TimeMark, but class was expected
	at io.kotest.engine.spec.interceptor.SpecFinishedInterceptor.intercept-0E7RQCE(SpecFinishedInterceptor.kt:37)
	at io.kotest.engine.spec.interceptor.SpecFinishedInterceptor$intercept$1.invokeSuspend(SpecFinishedInterceptor.kt)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)

do I need to wait for a new Kotest version? ** Not a contribution

Yep aiming for this weekend

The Kotest plugin seems to crash highlighting in IntelliJ, too, for a Kotlin 1.7.0 project. I assume that has the same root cause.

Any news about this issue?

There's a 5.3.1 release in progress that has 1.7 support.

Any news about this? I ran into this today with Kotest 5.4.5 and Kotlin 1.8.0 😞 I really want to use

kotlin.time.*

😭 This package has been incredibly unstable since it was first added in 1.3 😕

Use it in which place?

In a library ><

Oh and kotest is holding you back

Yes, my tests are failing with the

Found interface kotlin.time.TimeMark, but class was expected

error.

I'm waiting for compiler plugin api to go stable. Did you hear anything about that Simon ?

Nothing concrete. @dmitriy.novozhilov is talking about that compiler APIs on KotlinConf IIRC. I believe IR is going to be stable before FIR, but not entirely sure. cc\\ @raulraja

So not much chance of it being stable by 1.9 then

K2 Beta is targeted for 1.9, so I guess not. https://youtrack.jetbrains.com/issue/KT-52604/Release-K2-Beta Do you know about a workaround for the

kotlin.time

conflict?

The reason was that last time we bumped from 1.4 to 1.5 to 1.6 a ton of issues occurred. I guess we could release 5.6 targetting 1.8

Yes, it's an annoying. I've wanted to leverage plugins for many years, but have sadly stayed away from it for this reason. I hope it stabilises soon 🤞

Hey @simon.vergauwen, @sam, I ran into this issue when tried to use

kotlin.time.Duration

in one of the modules (not using Kotest). We’re currently using kotlin

1.6.21

and I’m guessing there’s no point upgrading just to fix this issue as you’re getting same in

1.8.0

. Do you know any workaround? As of now, I simply moved to

java.time.Duration

with coreLibraryDesugaring