Migrating from kapt to ksp gives error

I have a working Kapt processor, and I’ve move it over to KSP, its very basic, it just parses an json file and generates classes using KotlinPoet.

I’m using kotlin 1.5.31, ksp 1.5.31-1.0.0, and kotlinpoet 1.10.2

However, when running the ksp task never finished. I get the following error

 Task :xxx-client:kspMyBuildFlavorReleaseKotlin FAILED
 e: java.lang.StackOverflowError
         at java.base/java.lang.ClassLoader.defineClass1(Native Method)
         at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1017)
         at java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:174)
         at java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:800)
         at java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:698)
         at java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:621)
         at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:579)
         at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
         at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
         at org.jetbrains.kotlin.storage.LockBasedStorageManager$MapBasedMemoizedFunction.invoke(LockBasedStorageManager.java:593)
         at org.jetbrains.kotlin.storage.LockBasedStorageManager$MapBasedMemoizedFunctionToNotNull.invoke(LockBasedStorageManager.java:651)
         at org.jetbrains.kotlin.resolve.lazy.descriptors.AbstractLazyMemberScope.getContributedVariables(AbstractLazyMemberScope.kt:139)
         at org.jetbrains.kotlin.resolve.lazy.descriptors.LazyClassMemberScope.getContributedVariables(LazyClassMemberScope.kt:380)
         at org.jetbrains.kotlin.resolve.lazy.LazyDeclarationResolver$resolveToDescriptor$1.visitProperty(LazyDeclarationResolver.kt:182)
         at org.jetbrains.kotlin.resolve.lazy.LazyDeclarationResolver$resolveToDescriptor$1.visitProperty(LazyDeclarationResolver.kt:94)
         at org.jetbrains.kotlin.psi.KtProperty.accept(KtProperty.java:58)
         at org.jetbrains.kotlin.resolve.lazy.LazyDeclarationResolver.resolveToDescriptor(LazyDeclarationResolver.kt:94)
         at org.jetbrains.kotlin.resolve.lazy.LazyDeclarationResolver.resolveToDescriptor(LazyDeclarationResolver.kt:91)
         at org.jetbrains.kotlin.resolve.lazy.ResolveSession.resolveToDescriptor(ResolveSession.java:368)
         at com.google.devtools.ksp.processing.impl.ResolverImpl.resolveDeclaration(ResolverImpl.kt:440)
         at com.google.devtools.ksp.symbol.impl.kotlin.KSPropertyDeclarationImpl$propertyDescriptor$2.invoke(KSPropertyDeclarationImpl.kt:43)
         at com.google.devtools.ksp.symbol.impl.kotlin.KSPropertyDeclarationImpl$propertyDescriptor$2.invoke(KSPropertyDeclarationImpl.kt:42)
         at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
         at com.google.devtools.ksp.symbol.impl.kotlin.KSPropertyDeclarationImpl.getPropertyDescriptor(KSPropertyDeclarationImpl.kt:42)
         at com.google.devtools.ksp.symbol.impl.kotlin.KSPropertyDeclarationImpl.access$getPropertyDescriptor(KSPropertyDeclarationImpl.kt:34)
         at com.google.devtools.ksp.symbol.impl.kotlin.KSPropertyDeclarationImpl$getter$2.invoke(KSPropertyDeclarationImpl.kt:68)
         at com.google.devtools.ksp.symbol.impl.kotlin.KSPropertyDeclarationImpl$getter$2.invoke(KSPropertyDeclarationImpl.kt:65)
         at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
         at com.google.devtools.ksp.symbol.impl.kotlin.KSPropertyDeclarationImpl.getGetter(KSPropertyDeclarationImpl.kt:65)
         at com.google.devtools.ksp.processing.impl.ResolverImpl$collectAnnotatedSymbols$visitor$1.visitPropertyDeclaration(ResolverImpl.kt:325)
         at com.google.devtools.ksp.processing.impl.ResolverImpl$collectAnnotatedSymbols$visitor$1.visitPropertyDeclaration(ResolverImpl.kt:288)
         at com.google.devtools.ksp.symbol.impl.kotlin.KSPropertyDeclarationImpl.accept(KSPropertyDeclarationImpl.kt:103)
         at com.google.devtools.ksp.processing.impl.ResolverImpl$collectAnnotatedSymbols$visitor$1.visitClassDeclaration(ResolverImpl.kt:302)
         at com.google.devtools.ksp.processing.impl.ResolverImpl$collectAnnotatedSymbols$visitor$1.visitClassDeclaration(ResolverImpl.kt:288)
         at com.google.devtools.ksp.symbol.impl.kotlin.KSClassDeclarationImpl.accept(KSClassDeclarationImpl.kt:119)
         at com.google.devtools.ksp.processing.impl.ResolverImpl$collectAnnotatedSymbols$visitor$1.visitFile(ResolverImpl.kt:296)
         at com.google.devtools.ksp.processing.impl.ResolverImpl$collectAnnotatedSymbols$visitor$1.visitFile(ResolverImpl.kt:288)
         at com.google.devtools.ksp.symbol.impl.kotlin.KSFileImpl.accept(KSFileImpl.kt:61)
         at com.google.devtools.ksp.processing.impl.ResolverImpl.collectAnnotatedSymbols(ResolverImpl.kt:343)
         at com.google.devtools.ksp.processing.impl.ResolverImpl.access$collectAnnotatedSymbols(ResolverImpl.kt:104)
         at com.google.devtools.ksp.processing.impl.ResolverImpl$newAnnotatedSymbols$2.invoke(ResolverImpl.kt:354)
         at com.google.devtools.ksp.processing.impl.ResolverImpl$newAnnotatedSymbols$2.invoke(ResolverImpl.kt:353)
         at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
         at com.google.devtools.ksp.processing.impl.ResolverImpl.getNewAnnotatedSymbols(ResolverImpl.kt:353)
         at com.google.devtools.ksp.processing.impl.ResolverImpl.getSymbolsWithAnnotation(ResolverImpl.kt:280)
         at com.google.devtools.ksp.processing.Resolver$DefaultImpls.getSymbolsWithAnnotation$default(Resolver.kt:47)
         at dev.zacsweers.moshix.ksp.JsonClassSymbolProcessor.process(JsonClassSymbolProcessorProvider.kt:112)
         at com.google.devtools.ksp.AbstractKotlinSymbolProcessingExtension$doAnalysis$4$1.invoke(KotlinSymbolProcessingExtension.kt:186)
         at com.google.devtools.ksp.AbstractKotlinSymbolProcessingExtension$doAnalysis$4$1.invoke(KotlinSymbolProcessingExtension.kt:184)
         at com.google.devtools.ksp.AbstractKotlinSymbolProcessingExtension.handleException(KotlinSymbolProcessingExtension.kt:278)
         at com.google.devtools.ksp.AbstractKotlinSymbolProcessingExtension.doAnalysis(KotlinSymbolProcessingExtension.kt:184)
         at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM.analyzeFilesWithJavaIntegration(TopDownAnalyzerFacadeForJVM.kt:120)
         at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM.analyzeFilesWithJavaIntegration$default(TopDownAnalyzerFacadeForJVM.kt:86)
         at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler$analyze$1.invoke(KotlinToJVMBytecodeCompiler.kt:252)
         at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler$analyze$1.invoke(KotlinToJVMBytecodeCompiler.kt:243)
         at org.jetbrains.kotlin.cli.common.messages.AnalyzerWithCompilerReport.analyzeAndReport(AnalyzerWithCompilerReport.kt:113)
         at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.analyze(KotlinToJVMBytecodeCompiler.kt:243)
         at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.repeatAnalysisIfNeeded(KotlinToJVMBytecodeCompiler.kt:213)
         at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.repeatAnalysisIfNeeded(KotlinToJVMBytecodeCompiler.kt:213)
         at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.repeatAnalysisIfNeeded(KotlinToJVMBytecodeCompiler.kt:213)
         at org.jetbrains.kotlin.cli.jvm.compiler.KotlinToJVMBytecodeCompiler.repeatAnalysisIfNeeded(KotlinToJVMBytecodeCompiler.kt:213)

[ting-yuan]

Multi-round processing is designed for cooperation among processors. A typical use case is that a processor generates a file in round N and another processor picks it up in round N + 1. When there’s no new outputs, processors run to a fixed point and the entire processing terminates. KSP chose this somewhat implicit termination condition instead of having processors report an explicit flag, because it is a common approach in the communities when the API is designed.

In contrast to catching and ignoring the exception, you could also write the file once in SymbolProcessor.finish() if the generated files are not expected to be consumed by other processors.

[mistletoe5215]

@ting-yuan

i write the file once in SymbolProcessor.finish() ,but the build panel show the following warning info #786 to fix it