Issue on the Idea logs

[Aliaksandr Luferau]

Hello i see a lot of errors after latest update on the logs. Like this.

2021-03-18 08:55:36,000 [1872657]  ERROR - j.lang.folding.LanguageFolding - IntelliJ IDEA 2020.3.3  Build #IU-203.7717.56 
2021-03-18 08:55:36,000 [1872657]  ERROR - j.lang.folding.LanguageFolding - JDK: 11.0.10; VM: OpenJDK 64-Bit Server VM; Vendor: JetBrains s.r.o. 
2021-03-18 08:55:36,000 [1872657]  ERROR - j.lang.folding.LanguageFolding - OS: Windows 10 
2021-03-18 08:55:36,001 [1872658]  ERROR - j.lang.folding.LanguageFolding - Plugin to blame: Illuminated Cloud 2 version: 2.1.6.6 
2021-03-18 08:55:36,016 [1872673]  ERROR - j.lang.folding.LanguageFolding - Please change caller according to com.intellij.openapi.project.IndexNotReadyException documentation 
com.intellij.openapi.project.IndexNotReadyException: Please change caller according to com.intellij.openapi.project.IndexNotReadyException documentation
    at com.intellij.openapi.project.IndexNotReadyException.create(IndexNotReadyException.java:67)
    at com.intellij.util.indexing.FileBasedIndexImpl.handleDumbMode(FileBasedIndexImpl.java:756)
    at com.intellij.util.indexing.FileBasedIndexImpl.ensureUpToDate(FileBasedIndexImpl.java:708)
    at com.intellij.util.indexing.FileBasedIndexEx.processExceptions(FileBasedIndexEx.java:230)
    at com.intellij.util.indexing.FileBasedIndexEx.processValueIterator(FileBasedIndexEx.java:335)
    at com.intellij.util.indexing.FileBasedIndexEx.processValuesInScope(FileBasedIndexEx.java:304)
    at com.intellij.util.indexing.FileBasedIndexEx.getContainingFiles(FileBasedIndexEx.java:182)
    at com.illuminatedcloud.intellij.index.ApexNamespaceIndex.getTopLevelTypeDeclarations(SourceFile:80)

Today also saw strange error on the Log Analyzer:

And i have feeling that freezes appears when try to open some apex file from the project. Previously i don’t see this spinners at all

but for now this shown about 20 seconds per each file. Not sure if this related but

[Scott Wells]

Hi. I'm going to investigate the former for next week's build. As for the latter, can you provide a full stack trace? There hasn't been any work in that area in the last few builds so I'm not sure why that would suddenly happen. In fact, if you could share a full log that produces that error, that would be very useful. You can email it to [e-mail] if preferred.

[Scott Wells]

Both of these issues should be addressed in 2.1.6.7.