LSP :: Error from the Language Server: Method 'textDocument/documentLink' not supported. (Method not Found)

I am just starting to use GLSL on doom emacs. I am getting an error in lsp-glsl mode ( please see below ). Even the completions are not correct, meaning it is not giving completions for basic keywords like out , uniform. It gives a suggestion list on the pop up but not the correct one. However, flycheck red underline errors are visible. Below is the error I see.

Error on lsp-workspace-show-log [Trace - 12:52:25 AM] Sending request 'textDocument/documentLink - (55)'. Params: { "textDocument": { "uri": } }

[Trace - 12:52:25 AM] Received response 'textDocument/documentLink - (55)' in 5ms. Result: { "code": -32601, "message": "Method 'textDocument/documentLink' not supported." }

Versions : emacs 29.1 master 28fb02492 ~/.config/emacs/ doom 3.0.0-pre PROFILE=@0 grafted, HEAD -> master, origin/master, origin/HEAD 3191349 2023-09-14 20:17:24 +0200 ~/.config/doom/

Here is the lsp-describe-session output

-[-] glslls:41290 |-[-] Buffers | -[+] textures.vert -[-] Capabilities |-[X] workspaceSymbolProvider: nil |-[-] textDocumentSync: | |-[X] willSaveWaitUntil: nil | |-[X] willSave: nil | |-[-] save: | | -[X] includeText: nil | |-[X] openClose: t | -[X] change: 1 |-[-] signatureHelpProvider: | -[X] triggerCharacters: [] |-[X] renameProvider: nil |-[X] referencesProvider: nil |-[X] hoverProvider: t |-[X] experimental: nil |-[-] executeCommandProvider: | -[X] commands: [] |-[X] documentSymbolProvider: nil |-[X] documentRangeFormattingProvider: nil |-[-] documentOnTypeFormattingProvider: | |-[X] moreTriggerCharacter: [] | -[X] firstTriggerCharacter: |-[-] documentLinkProvider: | -[X] resolveProvider: nil |-[X] documentHighlightProvider: nil |-[X] documentFormattingProvider: nil |-[X] definitionProvider: t |-[-] completionProvider: | |-[X] triggerCharacters: [] | -[X] resolveProvider: nil |-[-] codeLensProvider: | -[X] resolveProvider: nil -[X] codeActionProvider: nil

Any help on this is highly appreciated. Thank you.

Any solutions? I met the same problem.

As per notice in the README, I don't maintain this project anymore and I'm searching for a new maintainer.