Can you try to upgrade and see if you get any error messages?

I just merged !28 (merged) and once you upgrade to 4.7.0 (Mason upgrade is in the making) or later you should see an error message in Neovim if something is wrong with your setup.

I merged !28 (merged) and when you upgrade to sonarlint-language-server 4.7.0 or later, you will see the correct error message in Neovim. Mason upgrade is on the way.

schrieveslaach (acd09b78) at 19 Jan 20:05

schrieveslaach (acd09b78) at 19 Jan 20:05

Hi,

lately I've been trying to package sonarlint.nvim for nixpkgs https://github.com/NixOS/nixpkgs/pull/377720 but I discovered an issue with how NodeJS binary is being passed.

If node is not inside PATH and executable, then it will break because the actual parameter to be passed to configure node executable is clientNodePath as you can see here on line 208 https://github.com/SonarSource/sonarlint-vscode/blob/master/src/extension.ts.

You can reproduce this bug by excluding node from your PATH like this

(I was using nvm for my tests in VM and I could reproduce it in this way on a PopOS fresh install).

After you exclude node from your PATH sonarjs extension will break silently (because sonarlint/canShowMissingRequirementsNotification was not enabled, but if you enable it you will actually see the error message from SonarLint), but if you pass clietNodePath argument with the correct path to your node executable then it will start working again.

Thanks again for this plugin 😄 and I would be happy to help you to implement this PR just in case

Based on https://github.com/SonarSource/sonarlint-language-server/pull/551 this commit enhances the handler sonarlint/canShowMissingRequirementsNotification to check if the sonarlint-language-server supports the error_only return value to make sure that missing setup requirements will shown as LSP standard window message.

Fixes #29

schrieveslaach (acd09b78) at 19 Jan 19:58

... and 6 more commits

schrieveslaach (bf981ea9) at 19 Jan 19:17

schrieveslaach (9cdc370b) at 05 Jan 10:32

schrieveslaach (1e7c703c) at 09 Dec 09:32

schrieveslaach (02c5d3ca) at 08 Dec 19:53

schrieveslaach (b1bfa8d7) at 08 Dec 19:33

... and 1 more commit

FYI, I've documentated the proxy configuration, see 9250c49c.

When you dont use connected mode, you have to explicitly enable all rules in config afaik. See #19

That is not 100% true. If you don't have any rules configuration in sonarlint.nvim, there are a set of rules loaded, but I don't know which logic is behind it. Once one starts using rules, only the ones in rules are loaded. If empty, none will be loaded and if no rules are enabled for the current language, you get no rules for that.

schrieveslaach (9250c49c) at 08 Dec 12:10

schrieveslaach (2f4d1b90) at 08 Dec 11:00

schrieveslaach (2f4d1b90) at 08 Dec 11:00

schrieveslaach (2f4d1b90) at 08 Dec 10:59

schrieveslaach (c0d97495) at 08 Dec 10:55

schrieveslaach (faddbf71) at 08 Dec 10:38

schrieveslaach (96c00823) at 08 Dec 10:28

schrieveslaach (99bc81d9) at 08 Dec 10:20

schrieveslaach (70b561b4) at 08 Dec 10:14

schrieveslaach (38c83a06) at 08 Dec 10:13

schrieveslaach (36f4fcee) at 01 Dec 09:40

@jeremieburtin, thank you very much for investing into this issue. @jeremieburtin, are you also working with a proxy or forced to use a proxy? If so, I would change the title of the issue.

After looking at the sources I decided to close this issue and don't implement this request.

To me this conventions is a local convention of the nvim-lspconfig plugin and not something that is pushed for across all LSP related plugins. Also, I don't see any activity related to this request in https://github.com/mrcjkb/rustaceanvim nor in https://codeberg.org/mfussenegger/nvim-jdtls.

As for the path to the compilation database I use the default one wich is ./compile_commands.json so I don't need to specify it explicitly.

Did you double check this statement? Looking at the sonarlint VSCode configuration spec, I see that they use an absolute path in the example:

Path to the active compilation database, e.g. `C:\\Repos\\MyProject\\compile_commands.json

Do you mind to provide a source definition of this conventions? I never heard of it and nvim-jdtls has no Lsp prefix in its commands.

@MKoseler, the config looks fine to me. Currently, the proxy might be an explanation why this is not working. Did you try if sonarlint for VScode works properly with setting up a connection? That would give us a good hint if it is related to a potential proxy issue or if it is due to some issue in sonarlint.nvim.

Also, you could try to debug sonarlint-language-server (if you are a Java dev) and see if you can find anything. Checkout this line in my dotfiles.

I guess, sonarlint-language-server fails because there is no analyzer present (checkout the -analyzers option). Also, for getting diagnostics for C, you need to specify the path to the compilation database (see here).

Java 17 should be fine.

schrieveslaach (ccf52586) at 06 Nov 12:17

Based on https://github.com/SonarSource/sonarlint-language-server/pull/551 this commit enhances the handler sonarlint/canShowMissingRequirementsNotification to check if the sonarlint-language-server supports the error_only return value to make sure that missing setup requirements will shown as LSP standard window message.

Fixes #29

schrieveslaach (0adb60a1) at 06 Nov 08:14

@jeremieburtin, are you certain that analyzers_path .."sonarjs.jar", points to correct path?

@mrt181, I see in your config that you enbaled sonarlint.nvim for CS only:

      filetypes = { "cs" },

Please, try with the additional file types.

I see rules = vim.empty_dict() in your LSP config. Can you remove it because look at the sonarlint.nvim README:

Rules can be configured, e.g. by turning them on or off, with the following configuration. Please note that rules = {} deactivates all rules.

Can you check following questions?

• Do you get a pop up in Neovim after changing the line locally?
• Can you tell me which sonarlint-language-server version you are using?
• Is there any error or suspicious message in :LspLog?

schrieveslaach (46a8007d) at 20 Oct 20:06

FYI: new attempt to fix it upstream, see https://github.com/SonarSource/sonarlint-language-server/pull/548

Can you try to adjust following code locally in your local sonarlint.nvim?

   config.handlers["sonarlint/canShowMissingRequirementsNotification"] = function()
      return true
   end

I think sonarlint.nvim swallows the notification. Meanwhile, I tried to improve upstream so that you get a proper message in Neovim.

4.3.1 should now be working without the custom init options. @coderkun, do you mind to try it without custom init options?

Cool, thanks for testing.

schrieveslaach (9ce2318b) at 04 Oct 10:09

When I use the new setup method via lspconfig then I get the error below.

https://github.com/mfussenegger/nvim-jdtls/?tab=readme-ov-file#via-lspconfig

Error executing vim.schedule lua callback: ...al/share/nvim/lazy/sonarlint.nvim/lua/sonarlint/java.lua:171: attempt to index field 'handl
ers' (a nil value)                                                                                                                       
stack traceback:                                                                                                                         
        ...al/share/nvim/lazy/sonarlint.nvim/lua/sonarlint/java.lua:171: in function 'init_config'                                       
        ...al/share/nvim/lazy/sonarlint.nvim/lua/sonarlint/java.lua:166: in function ''                                                  
        vim/_editor.lua: in function ''                                                                                                  
        vim/_editor.lua: in function <vim/_editor.lua:0>                                                                                 

I couldn't figure out how to delay or postpone sonarlint configuration after the nvim-jdtls has done it's init setup.

schrieveslaach (1d49a469) at 04 Oct 10:09

Fixes #36

schrieveslaach (e6b8ac4d) at 03 Oct 10:19

After changing my dotfiles to use also the new jdtls initialization, I could reproduce your recent error. Now, it should be working fine. Can you give it another try?

schrieveslaach (9ce2318b) at 03 Oct 10:07

I found another approach that's get rid of the dependency on language/status. Do you mind to check if this is working with new jdtls setup. With the old setup it works.

schrieveslaach (0eda4467) at 02 Oct 10:06

@azdanov, can you try !27 (merged) to see it that fixes the issue?