:jack_o_lantern: Spooky Gradle Build Errors! :ghost: As Halloween creeps closer, weโ€™re summoning ta...
m
๐ŸŽƒ Spooky Gradle Build Errors! ๐Ÿ‘ป As Halloween creeps closer, weโ€™re summoning tales of terror from your builds! ๐Ÿง›โ€โ™‚๏ธ๐Ÿ•ธ๏ธ Have you encountered any cryptic, spine-chilling build errors lately? The kind that are unhelpful or hard to understand for Gradle non-experts? ๐Ÿ•ท๏ธ๐Ÿ’€ 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. ๐Ÿ–ค Happy debugging! ๐ŸงŸโ€โ™‚๏ธ
๐ŸŽƒ 1
r
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.
๐Ÿ–ค 1
i
๐ŸงŸโ€โ™‚๏ธ https://youtrack.jetbrains.com/issue/KT-63285
๐Ÿ–ค 1
h
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.
๐Ÿ–ค 1