What's the best way to track down the cause of: ```> Task :integration-tests:ksp:kspTestKotlinWa...

# gradle

[eygraber]

What's the best way to track down the cause of:

> Task :integration-tests:ksp:kspTestKotlinWasmJs FAILED
w: duplicate library name: kotlin
e: warnings found and -Werror specified

[mbonnin]

https://youtrack.jetbrains.com/issue/KT-62653
https://youtrack.jetbrains.com/issue/KT-51110

[mbonnin]

Ah, you commented on those so probably not what you were looking for, sorry 😅

[eygraber]

It might be related to KT-62653 because there is some non-standard source set usage in this project so I'll look into that

[eygraber]

Looks unrelated 😓

[Jeff Lockhart]

I think KT-51110 is the root tracking issue. "kotlin" being the library does seem odd though. Is that the standard lib? You could print your dependency tree with ./gradlew :integration-tests:ksp:dependencies > dependencies.txt and search the output dependencies.txt for where different versions are stemming from.

[eygraber]

The only thing that looks out of place there is

|    +--- com.google.devtools.ksp:symbol-processing-api:1.9.21-1.0.15
|    |    \--- org.jetbrains.kotlin:kotlin-stdlib-jdk8:1.9.0
|    |         +--- org.jetbrains.kotlin:kotlin-stdlib:1.9.0 -> 1.9.21 (*)

I wouldn't expect ksp 1.9.21-1.0.15 to be depending on stdlib:1.9.0

[Jeff Lockhart]

Yeah, that's weird. There are a couple places KSP has kotlin("jvm") version "1.9.0" hardcoded:
github.com/google/ksp/blob/c619963715264613f6d4683e5bcf23b3ff0f2cbf/buildSrc/build.gradle.kts#L4
github.com/google/ksp/blob/c619963715264613f6d4683e5bcf23b3ff0f2cbf/build.gradle.kts#L23

[eygraber]

Even still, it looks like it's correctly getting switched to use 1.9.21

[Jeff Lockhart]

The way I understand this bug, it doesn't matter that transitive dependencies should be getting updated to the newer version declared by the project. For some reason Kotlin/JS and Kotlin/Native spit out that warning anyway.

[eygraber]

In this case it's only happening for wasmJs. js works fine

[Jeff Lockhart]

I guess Kotlin/Wasm is effected too. I see the warning myself for kotlinx-serialization in native targets:
> w: duplicate library name: org.jetbrains.kotlinx:kotlinx-serialization-core
because kotlinx-datetime declares 1.5.1 and I declare 1.6.1 in my tests. It might be the indirect relationship where, 1.5.1 is a transitive main dependency and 1.6.1 is introduced in tests.
I also see this in the dependencies output:

+--- org.jetbrains.kotlinx:kotlinx-datetime:0.4.1
|    \--- org.jetbrains.kotlinx:kotlinx-serialization-core:1.5.1 -> 1.6.1

[eygraber]

The underlying issue was relying on a library that was using the wasm target and not the wasmJs target