Omnisharp not working with LazyVim and bloating the lsp.log file (13GB+ and counting) about omnisharp-extended-lsp.nvim HOT 4 CLOSED

Hi,

From what I can see, it seems that OmniSharp LSP server is failing to initialize and then diagnostics are still trying to call the server, thus leading to all those log messages. This seems unrelated to this plugin, as it overrides specific handlers, not diagnostics ones. To confirm that, you could modify your config to remove the plugin and also any handler modifications.

One question that occurred to me is - does Hoffs/omnisharp-extended-lsp.nvim install OmniSharp/omnisharp-roslyn or am I supposed to be doing that manually?

This plugin does not perform any installation or configuration, it only builds on top of LSP. OmniSharp LSP configuration information can be found here - https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#omnisharp

from omnisharp-extended-lsp.nvim.

Looking around, I see from logs this has to do with csx files which have a bunch of issues related, e.g.:

• dotnet/vscode-csharp#4976 (comment)

I will close this because without dotnet script init or manually creating omnisharp.json with the following content: [...] nuget references are not supported.

• OmniSharp/omnisharp-roslyn#2405

Based on those, I would suggest trying one of the suggestions from those issues.

from omnisharp-extended-lsp.nvim.

You could also try to create a new dotnet project (dotnet new console) and see if issue persists.

from omnisharp-extended-lsp.nvim.

Thank you so much for looking into this. In a new dotnet project, go to definition (telescope_lsp_definitions()) appears to work after turning on the lang-omnisharp feature in :LazyExtras with no further configuration. I'll see if I can get references (telescope_lsp_references()) to work via custom LazyVim config.

I'll ask about the error flood in OmniSharp/omnisharp-roslyn too. Thanks again, really appreciate your help.

from omnisharp-extended-lsp.nvim.