A modern programming language that makes developers happier.

kotlinlang

:jack_o_lantern: *Spooky Gradle Build Errors!* :ghost:

As Halloween creeps closer, we’re summoning *tales of terror from your builds*! :male_vampire::spider_web:

Have you encountered *any cryptic, spine-chilling build errors* lately? The kind that are *unhelpful or hard to understand for Gradle non-experts*? :spider::skull:
We want to see the most baffling, eerie build error messages you’ve come across! Whether it’s a phantom failure or a ghostly stack trace, share your spooky stories here. :black_heart:

Happy debugging! :male_zombie:

This one took a while to get my head around:
<https://github.com/gradle/gradle/issues/30970>

Exception thrown trying to construct exception, obscuring the actual problem.

:ghost: <https://youtrack.jetbrains.com/issue/KT-71048>

:scream: <https://youtrack.jetbrains.com/issue/KT-70871/>

:male_zombie: <https://youtrack.jetbrains.com/issue/KT-63285>

Not a bug but scary things: the usage of custom state machine using coroutines inside KGP (causes no helpful stack traces, especially with Gradle CC) und the usage of internal Gradle classes, that can be changed by a new Gradle version.