Completions broke?

[CharlesIrvineKC]

Environment

• Elixir & Erlang versions (elixir --version): Erlang/OTP 26 [erts-14.2.1] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [jit:ns] [dtrace]

Elixir 1.16.0 (compiled with Erlang/OTP 26)

• VSCode ElixirLS version: 0.19.0
• Operating System Version: darwin 23.2.0

I just updated to the latest version of ElixirLS and my completions aren't working. If I type "def" and invoke completions, I just get "no suggestions".

Any suggestions on how I might trouble shoot? I've tried deleting my ".elixir_ls" dir and restarting vscode.

[CharlesIrvineKC]

If I load the previous version of ElixirLS (0.18.1) completions start working again. And, when I reload the most recent version (0.19.0), completions stop working.

[lukaszsamson]

Please post output logs, LSP message traces or a repo that reproduces this problem. I cannot reproduce that

[CharlesIrvineKC]

The only log file that looks suspicious is sharedProcess.log logs.zip

This is just a bare bones repo that I just created with: mix new complete_problem complete_problem.zip

I don't know where to find the "LSP message traces". I glad to send it if you tell me how to get it.

[CharlesIrvineKC]

When I invoke completions on test.ex, here is what I see:

[CharlesIrvineKC]

After I revert to version 0.18.3, I get the expected completions:

[lukaszsamson]

@CharlesIrvineKC https://github.com/elixir-lsp/vscode-elixir-ls#check-elixirls-output

[CharlesIrvineKC]

ElixirLS output logs:

exlixir_output.log

[lukaszsamson]

Your repo works on my machine.

Your logs look correct. You can also enable tracing in ElixirLS extension settings

You should then see something like this in the output tab

[Trace - 15:38:29] Sending request 'textDocument/completion - (13)'.
Params: {
    "textDocument": {
        "uri": "file:///Users/myuser/Downloads/complete_problem/lib/test.ex"
    },
    "position": {
        "line": 0,
        "character": 5
    },
    "context": {
        "triggerKind": 1
    }
}

[Trace - 15:38:29] Received response 'textDocument/completion - (13)' in 28ms.
Result: {
    "isIncomplete": true,
    "items": [
        {
            "command": {
                "command": "editor.action.triggerParameterHints",
                "title": "Trigger Parameter Hint"
            },
            "deprecated": false,
            "detail": "macro",
            "documentation": {
                "kind": "markdown",
                "value": "Defines a public macro with the given name and body."
            },
            "insertText": "defmacro $1 do\n\t$0\nend",
            "insertTextFormat": 2,
            "insertTextMode": 2,
            "kind": 21,
            "label": "defmacro",
            "labelDetails": {
                "description": "Kernel.defmacro/2",
                "detail": "(call, expr \\\\ nil)"
            },
            "sortText": "00000000",
            "tags": []
        },
        ...

[CharlesIrvineKC]

With verbose setting:

exlixir_output.log

[lukaszsamson]

ElixirLS extension is working correctly and returning completions. Please verify that no other extension is interfering. Please verify your VSCode settings - maybe some setting is filtering completions

[CharlesIrvineKC]

Did you ever check the sharedProcess.log file in the logs.zip file I posted? There was some suspicious stuff in the file I thought.

[lukaszsamson]

I did, all look OK

[CharlesIrvineKC]

I got out the big hammer. I deleted VS code and my settings, preferences, extensions etc, then reloaded ElixirLS and now completions are working. Who knows what the problem was exactly. Anyway, problem solved. Thanks for the help.