Philip Wedemann

I also got the same problem when using kotlinx-datetime: ```kotlin @Serializable data class MyDate(val myDate: Instant) val invalid = """{ "myDate": "fff" }""" Json.decodeFromString(MyDate.serializer(), invalid) ``` Results into this error...

With some expect/actual code its also possible to only add `Parcelable ` support instead adding the broken by design `java.io.Serializable` support. I did this here too: https://github.com/hfhbd/kotlinx-uuid/pull/297

What about adding it to `coroutines-test` instead? This would require adding `datetime` as a dependency to the test library too. While the use-case `TimeSource.toClock` also affects the stdlib `TimeSource`, (so...

Personally, I think, we should split sql declarations (including delete statements!) and actual user queries in separate files (and languages). This also allows us to get rid of the grouping...

This also does not work: https://scans.gradle.com/s/mapibsleenhye

According to the stacktrace, this error comes from IntelliJ, that's used under the hood as compiler platform (to parse the sql code). Unfortunately, the error message from IntelliJ is internal...

I don't think this has anything to do with the Gradle plugin, only IntelliJ usage in sql-psi and sqldelight.

Well, the exception comes from IntelliJ: ``` Caused by: java.io.IOException: Stream closed at com.intellij.openapi.util.registry.Registry.loadFromBundledConfig(Registry.java:137) ``` For some reasons the internal registry is closed during using it, maybe some other process...

You have a mismatch of sqldelight 2.0.1, sql-psi 0.4.8 and the sqldelight IntelliJ plugin 2.0.1.

0.4.8 Do you have some strange setup? 🤔