Hello, thank you for reporting this issue.
It seems that the extension is failing to activate for some reason.
I notice from your extract of the extension host log that the extension does seem to receive an activation event when opening a Python file, at which point it should spawn a Java process for the Language Server.
Could you please do the following:
- Put the following settings in your VSCode config
{
"sonarlint.output.showAnalyzerLogs": true,
"sonarlint.output.showVerboseLogs": true,
"sonarlint.trace.server": "verbose"
}
- Close all open editors, exit and restart VSCode
- Open the developer tools - “Help” > “Toggle Developer Tools”
- Select a Python file
At this point, any error thrown during the extension activation should be visible in the console. You can check whether the Language Server is started by executing the following command in a terminal (provided that the JAVA_HOME environment variable points to your OpenJDK 11 installation directory):
$ ${JAVA_HOME}/bin/jps
One of the lines output by jps should read sonarlint-ls.jar.
If this is not the case, maybe the extension is having trouble finding the right path to the JRE, in which case you can specify it with the sonarlint.ls.javaHome property.
Also, please note that the "sonarlint.trace.server": "verbose" property can result in a log of content in the SonarLint Output, so I would advise that you set it to "off" once SonarLint is back on its feet.