I don't see this problem from vscode and the completion order shown in the video doesn't seem to match what gopls is sending.

@anthony-S93 can you please capture the lsp trace (esp textDocument/completion message)? And if possible, can you also capture the lsp textDocument/completion messages from other language servers? That will help us understand what gopls is doing differently.

Thank you for the quick response. So I've dug thorugh my LSP logs and managed to isolate the logs that were produced right after I activated the completion feature shown in the video above. Here are the logs for the different language servers I re-tested:

1. gopls
2. pyright

I also tested tsserver, but tsserver didn't produce output logs at all when I invoked autocompletion.

Please note that logs I sent were for when the language servers were running in "single-file" mode, which simplifies the logs. In any case, gopls exhibited the same behavior with or without any root markers in the project directory.

Thank you for your time. And please let me know if there is any additional information you need.

Update:
@hyangah
Here is something else I discovered upon further testing. If I use autocompletion to complete fmt instead of typing it manually like I did in my original report, the autocompletion behaves normally. Like so:

The correct behavior did not produce any logs.

For completeness' sake, here is a video showing the autocompletion behavior when I typed the entire string "fmt" manually.

Hi, in the logs you shared (https://pastebin.com/raw/Wm4j0FPG), I can see that 'preselect' is only set for the first item in the list. So this looks like a bug in your LSP client. I also can't reproduce in either VS Code or coc.nvim.

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)

Hi, in the logs you shared (https://pastebin.com/raw/Wm4j0FPG), I can see that 'preselect' is only set for the first item in the list. So this looks like a bug in your LSP client. I also can't reproduce in either VS Code or coc.nvim.

I looked deeper into this and discovered what's causing the issue. As it turns out, the completion engine I'm currently using will choose the ordering of the items in the completion list dynamically—based on the occurence of the completion item within the document itself. Here's a brief video to demonstrate this behavior:

However, this dynamic reordering of the completion list by the completion engine does not work well with gopls, which always assumes dictionary ordering of the completion list and then preselects the first item in said list. Both gopls and the completion engine are working on different assumptions with regards to the order of the completion list items, and that's what's causing the issue.

The Workaround:
If you're using gopls with neovim and using nvim-cmp + cmp-nvim-lsp for completion, add the following code to your nvim-cmp's config:

local cmp = require("cmp")
cmp.setup({
    -- Your own cmp config is here...
    
    -- Add the following config to turn off preselect
    preselect = cmp.PreselectMode.None
})

What this does is that it instructs nvim-cmp to ignore preselections by the LSP.