IssueMatcher$NoMatchException: Start line number (254) larger than lines in file: 254


(Julien Herr) #1


Since my last update of PhpStorm, I often see the following random exception and I don’t know how to reproduce.

  • versions used (SonarQube, Scanner, Plugin, and any relevant extension)
    SonarLint: Version:
    PhpStorm 2018.2 EAP
    Build #PS-182.3208.33, built on June 13, 2018
    JRE: 1.8.0_152-release-1226-b7 x86_64
    JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
    macOS 10.13.4

  • error observed
    Error finding secondary location for issue
    Details: php:S1192

    org.sonarlint.intellij.issue.IssueMatcher$NoMatchException: Start line number (254) larger than lines in file: 254
      at org.sonarlint.intellij.issue.IssueMatcher.getIssueTextRange(
      at org.sonarlint.intellij.issue.IssueMatcher.match(
      at org.sonarlint.intellij.issue.IssueProcessor.transformFlows(
      at org.sonarlint.intellij.issue.IssueProcessor.transformIssue(
      at org.sonarlint.intellij.issue.IssueProcessor.transformIssues(
      at org.sonarlint.intellij.issue.IssueProcessor.process(
      at org.sonarlint.intellij.analysis.SonarLintJobManager.lambda$null$1(
      at com.intellij.openapi.progress.impl.CoreProgressManager.a(
      at com.intellij.openapi.progress.impl.CoreProgressManager.a(
      at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(
      at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(
      at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(
      at org.sonarlint.intellij.analysis.SonarLintJobManager.lambda$runTask$2(
      at java.util.concurrent.Executors$
      at java.util.concurrent.ThreadPoolExecutor.runWorker(
      at java.util.concurrent.ThreadPoolExecutor$

(Tibor Blenessy) #2

Hello Julien,

can you identify the file which is being analyzed? It should be one in the active editor window. If are able to identify the file, can you share it here?

(Julien Herr) #3

I will try to do it the next time a see the issue.
But I’ve not reproduced it this week. Maybe it was related to a cache or something like that.

BTW, maybe it is possible to have more details in the IntelliJ error window because it is not easy to understand the information you need for the debug and then provide it :slight_smile:

(Hirle) #4