A modern programming language that makes developers happier.

kotlinlang

I keep getting
```Changing log factory from com.pinterest.ktlint.core.internal.LoggerFactory to com.pinterest.ktlint.core.internal.LoggerFactory
java.lang.Throwable                  
        at org.jetbrains.kotlin.com.intellij.openapi.diagnostic.Logger.logFactoryChanged(Logger.java:76)   
        ...40 other lines```
which is mildly annoying :slightly_smiling_face:

related issues:
• <https://github.com/jeremymailen/kotlinter-gradle/issues/254>
• <https://github.com/jeremymailen/kotlinter-gradle/issues/110>
• <https://github.com/pinterest/ktlint/issues/1497>
All issues point to some kind of non-determinism, and I didn’t manage to pin down when it exactly happens and when it doesn’t.
The stack trace goes through <https://github.com/pinterest/ktlint/blob/764135dde88e0a9c695eb2dfa5f6fd39012b790d/ktlint-core/src/main/kotlin/com/pinterest/ktlint/core/internal/KotlinPsiFileFactory.kt#L43|this place in ktlint> and <https://github.com/JetBrains/intellij-community/blob/fd227801667eb642210aa7cca37d76039c648073/platform/util/src/com/intellij/openapi/diagnostic/Logger.java#L79|this place in intellij-community> which actually prints the stack trace: `ExceptionUtil.getThrowableText(new Throwable())`. It’s generally unusual to print such stack trace unless some debug API is called.

How about we try to remove this track trace, i.e. contribute to intellij-community? Then this log will produce a single line which won’t be painful. Alternatively, we can try to use a proper logger and print the stack trace if DEBUG level is enabled, but it might be a chicken-egg problem since we’re changing logger factories, so which logger should we use?
WDYT?