This message was deleted.
# community-support
s
This message was deleted.
c
A few ideas: • start with a clean Gradle daemon (
./gradlew daemon --stop
) • Grab a thread dump of the Gradle daemon to see what the threads are doing (
jps
to list java processes,
jstack
to get a thread dump) • Comment out the contents of build.gradle.kts and incrementally add parts back in to identify the offending code
👍 1
Sometimes the caches needs to be fully cleared - remove ~/.gradle/caches directory
e
I think Kotlin will start a compiler daemon by default as well, and perhaps that is stuck