fyi looks like an accidental duplicate in the 1.7.20 release notes

Is it right that Fleet is expected to have no autocompletion for KTS files at present?

🎉 Kotlin 1.8.0-Beta brings the following updates: ✅ Gradle 7.3 compatibility ✅ Recursive

Path

utility functions in the stdlib ✅ Support for Xcode 14 in Kotlin/Native ✅ Discontinuation of support for the old JVM backend Try it out and share your feedback! 👉 https://kotlinlang.org/docs/whatsnew-eap.html

Can't update multiplatform project (kotlin jvm + kotlin js), because of NodeJsRootPlugin

Failed to apply plugin class 'org.jetbrains.kotlin.gradle.targets.js.nodejs.NodeJsRootPlugin'.
> Could not create an instance of type org.jetbrains.kotlin.gradle.targets.js.nodejs.NodeJsRootExtension.
   > IdeaSyncDetectorVariantFactory type is not known for plugin variants

Threading my notes on 1.8.0-Beta testing here for posterity

Any reason for the capital 'B' in

1.8.0-Beta

? Not that I mind at all, mainly curious if I should do the same for my own libraries?

Why install Beta? ➡️ If you work on a complex multi-module project, it may streamline your experience when you adopt the Stable release version. ➡️ If you’re a library author, working with EAP versions allows you to support the latest Kotlin versions in your library almost immediately with the Stable release, which makes your users happier and your library more popular. ➡️ If you’re a Kotlin enthusiast and enjoy contributing to the Kotlin ecosystem by creating educational content, trying new features in the Kotin EAP allows you to be among the first to share the experience of using the new cool features with the community. Let us know if one of these descriptions applies to you by voting below this message. Respond with 1️⃣ if you’re working on a complex multi-module project 2️⃣ if you are a library author 3️⃣ if you are a Kotlin enthusiast

1.8 gradle plugin introduces breaking change in

cssSupport

changing

enabled

from field to property without proper documentation.

Jupyter plugin does not work on 1.8.0-Beta

Using additional configuration with

js

block in gradle after

js(IR)

gives error:

==========
This project currently uses the Kotlin/JS Legacy compiler backend, which has been deprecated and will be removed in a future release.
Please migrate the project to the new IR-based compiler (<https://kotl.in/jsir>) by adding:
- kotlin.js.compiler=ir to your gradle.properties file.
- js(IR) { ... } to your build file.
You can continue to use the deprecated legacy compiler in the current version of the toolchain by specifying it explicitly.
==========

Before it automatically used first provided compiler. I think since LEGACY is deprecated,

js

should mean IR by default.

@Ilya Goncharov [JB] kotlin-js-store is still in the root. It would be much better to move it to

gradle

Running into this compilation error with our Kotlin JS project with 1.8.0-Beta (works fine in 1.7.21) Not sure if there’s a way to log exactly which class is failing to generate a TS definition… https://pastebin.com/FpDaAuus

Hi everyone! We’re starting the EAP Champions program and invite you to join! 🤔 Why do we need this program? While every EAP participant is very helpful, it’s invaluable to have direct contact with people who test each release on the same project. The majority of EAP participants currently use it with hobby projects, so we lack feedback from projects with a huge codebase. To make sure that all scenarios and project types are tested with the new Kotlin version, we’re starting the EAP Champions program and invite you to join! ✔️ You can become an EAP champion if you: • Work on a project that has the relevant attributes: 100+ module Android projects / 100+ module server-side projects with Ktor and Spring / Production projects that have KMM modules / Popular JVM/Multiplatform libraries. • Are ready to spend a couple of hours over 2 weeks testing each new release. • Have already reported issues to YouTrack, or understand how reporting works. • Are excited to participate and make an invaluable contribution to Kotlin’s development. 🥇 Why is being an EAP champion worthwhile? • It’s a great help to the Kotlin team and the community in general. • We’ll mention you or your projects in the Kotlin documentation and release blog posts. • For each champion who participates in the testing of 4 releases, we’ll send a special “EAP Champion Pack” – unique merch from JetBrains. • If you encounter critical problems in your projects, Kotlin engineers will do their best to provide you with assistance in fixing them or finding a workaround. ➡️ BECOME AN EAP CHAMPION ⬅️

I see this ambiguous function call warning with 1.8.0-RC-268. Should I report it?

🚀 Kotlin 1.8.0-RC is out with: ✅ Gradle 7.3 compatibility ✅ Recursive

Path

utility functions in stdlib ✅ Support for Xcode 14.1 in Kotlin/Native ✅ Discontinuation of support for the old JVM backend Help us put the finishing touches 🪄 on the RC by reporting any lingering issues in YouTrack: https://kotl.in/issue

I’m seeing this warning emitted from KGP in a project that does appear to set the JVM target to 11, wondering if this is a bug I should file or something I’m missing

> Task slack plugincompileTestKotlin

‘compileTestJava’ task (current target is 11) and ‘compileTestKotlin’ task (current target is 1.8) jvm target compatibility should be set to the same Java version.

By default will become an error since Gradle 8.0+! Read more: https://kotl.in/gradle/jvm/target-validation

Consider using JVM toolchain: https://kotl.in/gradle/jvm/toolchain

Repro: https://github.com/slackhq/slack-gradle-plugin/pull/166 CC @tapchicoma

I’ve got a sort of odd case here where I have a function that returns

Single<Collection<Type>>

and internally code that looks like this

return someListSingle.map { list -> list as Collection<Type> }

In 1.8.0-RC, this cast is marked as redundant (as a compilation warning), but removing it actually causes a compilation error. I’m not sure if it’s expected to automatically infer the cast or if I should report a bug for a false-positive warning.

I’m seeing these errors emitted and failing compilations when using Compose Compiler

1.4.0-dev-k1.8.0-RC-4c1865595ed

(from here) and Kotlin 1.8.0-RC, but I’m not sure where to start in diagnosing them or which issue tracker to report it on. No other context given in the compilation either

e: Source file or directory not found: plugin:androidx.compose.compiler.plugins.kotlin:sourceInformation=true
e: Source file or directory not found: plugin:androidx.compose.compiler.plugins.kotlin:liveLiterals=true

Would it be worth filing a FR to print out more diagnostic information for where these are being set? I’m unable to see where this is being set in our build without using a debugger to breakpoint calls to that

> Task :apps:app-legacy:compileInternalDebugUnitTestKotlin
kotlinOptions.freeCompilerArgs were changed on task :apps:app-legacy:compileInternalDebugUnitTestKotlin execution phase: -progressive, -Xinline-classes, -Xjsr305=strict, -opt-in=kotlin.contracts.ExperimentalContracts, -opt-in=kotlin.experimental.ExperimentalTypeInference, -opt-in=kotlin.ExperimentalStdlibApi, -opt-in=kotlin.time.ExperimentalTime, -Xassertions=jvm, -Xemit-jvm-type-annotations, -Xproper-ieee754-comparisons, -Xjvm-default=all, -Xtype-enhancement-improvements-strict-mode, -Xjspecify-annotations=strict, -Xenhance-type-parameter-types-to-def-not-null, -Xself-upper-bound-inference, -Xskip-prerelease-check, -P, plugin:androidx.compose.compiler.plugins.kotlin:suppressKotlinVersionCompatibilityCheck=1.8.0-RC2-330, -opt-in=com.slack.eithernet.ExperimentalEitherNetApi, -opt-in=com.slack.eithernet.ExperimentalEitherNetApi, -opt-in=com.slack.eithernet.ExperimentalEitherNetApi, -Xplugin=/Users/zacsweers/.gradle/caches/modules-2/files-2.1/androidx.compose.compiler/compiler/1.4.0-dev-k1.8.0-RC-4c1865595ed/70f3ba3161f2b13d7a24fcbd31d77cd103566985/compiler-1.4.0-dev-k1.8.0-RC-4c1865595ed.jar, -P, plugin:androidx.compose.plugins.idea:enabled=true, -Xallow-unstable-dependencies
This behaviour is deprecated and become an error in future releases!

Kotlin 1.8.0-RC2 has been released!K

Did something change between RC2 and release in the kotlin-bom around tests? RC2 was passing for us on CI, but with the final release I see some esoteric gradle conflicts around the kotlin test libraries. Lmk if I should file a bug

Hello! I'm playing around with the new context receivers prototype (really exciting!) and I've hit a little snag with function references. I'm trying to run a function of the following type:

suspend context(Foo, Bar) () -> Unit

, however its

.invoke

method is requiring two arguments, one for each receiver. The thing is: I explicitly have the receiver for one of them, but the other one is also a context receiver of the callee, so it isn't available as

this

. Is there any way I can call this function? Thank you!

👋 Hi, while testing Kotlin 1.8.20-Beta, we encounter this error during Gradle's configuration phase:

Failed to notify project evaluation listener.

* Exception is:	
org.gradle.api.ProjectConfigurationException: A problem occurred configuring project ':app'.
[...]
Caused by: org.gradle.internal.event.ListenerNotificationException: Failed to notify project evaluation listener.
[...]
Caused by: java.lang.ClassNotFoundException: org.jetbrains.kotlin.gradle.plugin.mpp.pm20.KotlinCompilationData

Here is a link to the corresponding Gradle scan: https://scans.gradle.com/s/prh6uvc24qqs6

I’m unable to find a 1.8.20-Beta (or 1.8.10) IDE plugin available in the EAP channel in IntelliJ 2023.1 EAP. Should I file an issue?

👋 I am not able to gradle-sync my project after updating the Kotlin IJ plugin to 1.8.20-Beta - I opened the issue here. Update: looks like it was due to using 1.6.10 during sync in our project (a workaround for older issues with KMP). Removing this hack resolves the issue!

1.8.20-Beta’s IDE plugin inspection for opt-in annotations doesn’t offer the option to add them https://youtrack.jetbrains.com/issue/KT-56528

I noticed that FIR in 1.8.20-Beta uses 0-index now for line numbers rather than 1. Want to check if that’s intended behavior first before filing a bug

I’m getting an incremental compilation issue with Android unit test compilation with 1.8.20-Beta which has the new incremental compilation on by default. https://youtrack.jetbrains.com/issue/KT-56423/Test-Incremental-Compilation-fails-with-Ca[…]o.-Check-your-module-classpath-for-missing-or-conflicting

Does anyone has any issues with linking native binaries on linux/macos with kotlin 1.8.20-Beta? like: • https://github.com/whyoleg/cryptography-kotlin/actions/runs/4151887365/jobs/7182476137:

e: /home/runner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/kotlinx-coroutines-test-linuxx64/1.6.4/4757f4ccaeca3c186c03adb80dd4125932850259/kotlinx-coroutines-test is cached (in /home/runner/.gradle/konan/kotlin-native-prebuilt-linux-x86_64-1.8.20-Beta/klib/cache/linux_x64-gSTATIC/org.jetbrains.kotlinx:kotlinx-coroutines-test/unspecified/1e60851fbe3383bc94735442f181a9273d1e96adaab6fe4b95811738dc5e378e/org.jetbrains.kotlinx:kotlinx-coroutines-test-cache/bin/liborg.jetbrains.kotlinx:kotlinx-coroutines-test-cache.a), but its dependency isn't: /home/runner/.gradle/konan/kotlin-native-prebuilt-linux-x86_64-1.8.20-Beta/klib/common/stdlib

• https://github.com/rsocket/rsocket-kotlin/actions/runs/4152472478/jobs/7183450649

e: /home/runner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/atomicfu-linuxx64/0.19.0/e5e28a197f697b77d49846bfec2fce6e0847e5ed/atomicfu is cached (in /home/runner/.gradle/konan/kotlin-native-prebuilt-linux-x86_64-1.8.20-Beta/klib/cache/linux_x64-gSTATIC/org.jetbrains.kotlinx:atomicfu/unspecified/7ec08e59096adf58ceb23075044b5b12968ce418b16d8d23364485d49f5fe48c/org.jetbrains.kotlinx:atomicfu-cache/bin/liborg.jetbrains.kotlinx:atomicfu-cache.a), but its dependency isn't: /home/runner/.gradle/konan/kotlin-native-prebuilt-linux-x86_64-1.8.20-Beta/klib/common/stdlib

or

e: /home/runner/.gradle/caches/modules-2/files-2.1/io.ktor/ktor-utils-linuxx64/2.2.3/1f96940f71493794b49a4fe22d25e448ae663854/ktor-utils is cached (in /home/runner/.gradle/konan/kotlin-native-prebuilt-linux-x86_64-1.8.20-Beta/klib/cache/linux_x64-gSTATIC/io.ktor:ktor-utils/unspecified/cd659155ccdeccb8b955ac996626c4018e6b1b19d85023c63b5d72de04e3affe/io.ktor:ktor-utils-cache/bin/libio.ktor:ktor-utils-cache.a), but its dependency isn't: /home/runner/.gradle/konan/kotlin-native-prebuilt-linux-x86_64-1.8.20-Beta/klib/common/stdlib

There seems to be a regression with the IR backend for the stub generating task in Kotlin 1.8.20-Beta. This wasn’t an issue with Kotlin 1.8.10. https://youtrack.jetbrains.com/issue/KT-56635/ I’ve added steps to reproduce the issue and provided as much information as I can. Please let me know if I can help more.