Anybody having issues with provisioning or it is j...
# kotlin-toolchain
r
Anybody having issues with provisioning or it is just me? After a
./kotlin clean
, provisioning of JDK and PNPM never finishes. I was able to bypass the JDK issue, using sdkman, yet the PNPM issue remains. Every module that declares
wasmJs
target, while executes a task "installing npm dependencies" waits for "downloading PNPM 11.9.0" Any idea on how to bypass this? • kotlin : v0.13.0 • jdk : 25 • os: linux
😱 2
👍 1
A workaround : Pre-seed the cache
Copy code
curl -sSL --fail -o ~/.cache/JetBrains/Kotlin/download.cache/d30df19002-pnpm-linux-x64.tar.gz \
    <http://github.com/pnpm/pnpm/|github.com/pnpm/pnpm/>…/pnpm-linux-x64.tar.gz
  # sha256: 8d987d82585453bcf260ea5d0bae346d298f1a5e71bcde8d99976521408ad895
j
Thanks a lot for the report. It seems GitHub releases downloads have changed their response and now one header exceeds some hardcoded internal limit. I'll fix ASAP
🚀 6
A little follow-up here. The issue linked in this thread was marked as duplicate of KTC-6078 - we had several reports at the same time. While I was working on the fix, there was another unrelated issue that prevented me from merging immediately. However, the next day (on Sunday), things went back to normal, GitHub no longer sent this huge header. This is why there was no urgency anymore, so it might seem there was no progress here. That said, KTC-6078 is still a thing. If a header exceeds 8kB, the Ktor CIO engine crashes with no way to configure the limit (KTOR-5613). So the fix (switching to another Ktor engine) is still relevant and will be merged.
👍 1
r
Hi @joffrey I am not sure if the issue with the github header has been fixed. I am trying to use kotlin via the github action provided by @irus (github.com/Heapy/setup-ktc) and I have the impression the PNPM problem is still present I will try to verify it
j
Are you still seeing
TooLongLineException: Line exceeds limit of 8192 characters
? Since my last message, I did merge the fix for KTC-6078, and it is available in 0.14.0-dev-4563, so you can try to bump to the latest dev version to see if the problem is resolved
r
@joffrey My bad. No, the issue is not present. Thanks for your interest
👍🏼 1
j
Ok great to hear!