You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a large project is imported into workspace, the JavaIndexer start indexing the files. And it also start indexing the binary files in kotlin_bin folder. While this is running if we trigger a rebuild by checking kotlin jvm level or change any files we end up with warning in java indexer as well as errors from semantic highlighter and kotlin analysis. Not sure if these processes are depending on the java index or they are mainly working on the kotlin_bin folder which is being cleared part of the rebuild.
This needs further investigation to provide a proper fix.
The text was updated successfully, but these errors were encountered:
When a large project is imported into workspace, the JavaIndexer start indexing the files. And it also start indexing the binary files in kotlin_bin folder. While this is running if we trigger a rebuild by checking kotlin jvm level or change any files we end up with warning in java indexer as well as errors from semantic highlighter and kotlin analysis. Not sure if these processes are depending on the java index or they are mainly working on the kotlin_bin folder which is being cleared part of the rebuild.
This needs further investigation to provide a proper fix.
The text was updated successfully, but these errors were encountered: