I m getting a `StackOverflowError` when I try to to generate

Question

I m getting a `StackOverflowError` when I try to to generate interfaces with SQLDelight 2 0 0 alpha05 `app cash sqldelight gradle SqlDelightTask$GenerateInterfaces` ``` gt Failed to compile CREATE VIRTUAL TABLE bookfts USING fts5 book id title ``` I m not sure if I m doing something wrong or if it s a bug ```Caused by java lang StackOverflowError at com intellij openapi progress impl CoreProgressManager isInNonCancelableSection CoreProgressManager java 774 at com intellij openapi progress impl CoreProgressManager doCheckCanceled CoreProgressManager java 134 at com intellij openapi progress ProgressManager checkCanceled ProgressManager java 211 at com intellij openapi progress ProgressIndicatorProvider checkCanceled ProgressIndicatorProvider java 23 at com intellij psi impl source tree CompositeElement getPsi CompositeElement java 687 at com intellij psi impl source SourceTreeToPsiMap treeElementToPsi SourceTreeToPsiMap java 16 at com intellij psi impl source tree SharedImplUtil getParent SharedImplUtil java 33 at com intellij extapi psi ASTWrapperPsiElement getParent ASTWrapperPsiElement java 19 at com alecstrong sql psi core psi SqlColumnReference unsafeResolve$core SqlColumnReference kt 33 at com alecstrong sql psi core psi SqlColumnReference$resolved$1 invoke SqlColumnReference kt 22 at com alecstrong sql psi core psi SqlColumnReference$resolved$1 invoke SqlColumnReference kt 20 at com alecstrong sql psi core ModifiableFileLazy forFile ModifiableFileLazy kt 22 at com alecstrong sql psi core psi SqlColumnReference resolve SqlColumnReference kt 28 at app cash sqldelight core lang util ColumnDefSourceKt columnDefSource ColumnDefSource kt 11 ``` the last line is where the stack overflow is occurring It works if I specify typenames `fts5 notindexed=book id INTEGER title TEXT ` although the sqlite documentation says it s wrong to add them in fts5 and that they re not needed and are in fact ignored in fts3 4

Manuel Pérez Alcolea · Answer

I reported this bug and it seems it s been fixed