With Kotlin 2.2.0 I'm seeing a ton of ```> Task :k...

# javascript

[CLOVIS]

With Kotlin 2.2.0 I'm seeing a ton of

> Task :kotlinNpmInstall FAILED
error <https://registry.yarnpkg.com/webpack-merge/-/webpack-merge-4.2.2.tgz>: Extracting tar content of undefined failed, the file appears to be corrupt: "ENOENT: no such file or directory, open '/usr/local/share/.cache/yarn/v6/npm-webpack-merge-4.2.2-a27c52ea783d1398afd2087f547d7b9d2f43634d-integrity/node_modules/webpack-merge/lib/join-arrays.js.map'"

across all my projects, across all CI runners, with different packages. Do we know what could cause this?

At the moment, it's hard to upgrade because all JS pipelines fail more than ~50% of the time

[Robert Jaros]

I've got the same problems.

[Robert Jaros]

Can't build directly on github actions but also can't in a docker container.

[Robert Jaros]

After some attempts today I assumed there is something wrong with github.

[Robert Jaros]

But as you are probably running Gitlab CI ...

[turansky]

We use NPM instead of Yarn and have no such problems

[CLOVIS]

Yep, GitLab CI on my side, also reproducible locally

[Robert Jaros]

I'm trying with kotlin.js.yarn=false now ...

[Robert Jaros]

Seems to work now

[Edoardo Luppi]

Tho it should still be working with Yarn. npm is not the default yet.
Worth reporting

[CLOVIS]

I'm trying it as well…

[CLOVIS]

Yep, no problems either with NPM

[Oliver.O]

You're using the build cache, right? Then it's probably https://youtrack.jetbrains.com/issue/KT-78504.

For a workaround, see https://github.com/infix-de/testBalloon/commit/a76cebeb35b03fbdf55ba5d9784f13f7a4c8e400

[CLOVIS]

I do use build cache, but it's not enabled in my CIs at the moment…

[Oliver.O]

Hmm, in my case it is clearing the GH action cache that makes a failed build work again... But though I've applied the above workaround, this thing is still hitting me now and then. Maybe it's time to abandon Yarn in KGP.

[Edoardo Luppi]

Doesn't that (--network-concurrency 1) mean installing packages will take longer?

[Edoardo Luppi]

And it would have been interesting to understand why it did not happen in previous releases.

[Oliver.O]

To me it seems that the --mutex network option is the important one. Otherwise, Gradle could spawn parallel Yarn invocations via KGP, and these invocations would not synchronize with each other, leading to file corruption. Could it be a factor that Gradle is increasingly using parallelism where it did not use it before? In my case, Gradle 8.14.2 runs parallel tasks even with org.gradle.parallel=false.

[Edoardo Luppi]

Yup I agree with you. Are you going to post a comment there about it, or I'm gonna go for it?

[Oliver.O]

The comment idea is yours, so feel free!

[Edoardo Luppi]

Posted, let's see.

[Robert Jaros]

This is an old Yarn issue - https://github.com/yarnpkg/yarn/issues/2629 . But I wonder why it is showing up now for us? Perhaps because KGP 2.2.0 runs two Yarn processes - for js and for wamsJS targets?

[Oliver.O]

That makes sense. The Wasm/JS and JS separation is new.

[Edoardo Luppi]

But does that mean the problem appears only when both targets are enabled? @CLOVIS what's your setup?

[Artem Kobzar]

@Ilya Goncharov [JB] ^^

[Oliver.O]

Quick update: Still had GH cache issues after applying the workaround for Yarn. Switched to Npm. No issues so far.