I'm not OP but I'm experiencing the same issue.
Here's my prettybarebones config. I just have the defaulteditor.snacks_picker enabled inLazyExtras.

Are you also using fzf-lua, like op? If you have a command like:Fzf<tab> then it's fzf lua

I assume it's fzf for me.

Are you also using fzf-lua, like op? If you have a command like:Fzf<tab> then it's fzf lua

The only thing popping up for:Fzf was this
.

Although I just ran a sync and it seems to be fine now!

I'm on v0.11.2 (mac) and v0.11.4 (linux/ubuntu), both have the same configuration (synced between two machines) and both show the same symptoms. All plugins are up to date (<leader>lU).

So remove those mappings you added. Does it then work as expected?

The correct gr/gd mappings are only added in buffers that have LSP attached that provide definitions/references, so to test you have to be in an actual buffer with LSP attached

So remove those mappings you added. Does it then work as expected?

It is working now. I will have to use it more to see if it works consistently now.
(I have kept updating all plugins throughout the day)

that's what I figured. Like I said I fixed that exact issue, but your "work-around" actually did exactly the opposite of what you wanted, so that's why it didn't work for you.

fyi, I removed that work-around from the description here, so that other users don't just copy that in their config without reading everything

gotcha, done.

will update how it goes (probably tomorrow again).

NVIM v0.11.5Build type: ReleaseLuaJIT 2.1.1741730670

Unfortunately it is still happening occasionally. I have not found a reliable way to reproduce it, but thatLspRestart pyright fixes it.

Did you try the steps from thiscomment to test with a fresh LazyVim installation? And only enable the Python Extra, don't copy over any of your personal configuration.

You might also be interested in settingvim.g.lazyvim_python_lsp = "basedpyright" in your~/.config/lazytest/lua/config/options.lua to makebasedpyright the default LSP server for Python to see if that makes any difference compared topyright. And just to make sure, also open Mason UI with<leader>cm and ifpyright is installed then go with your cursor on the wordpyright and pressX (capitalx) to uninstall it because Mason does not support automatic uninstallation of LSP servers.

I haven't, given it happens sporadically and I cannot reproduce it, I would have to work with minimum config for a while which is nearly impossible, Neovim custom config is just too awesome! But I am doing it now, will post an update (edit: done, seenext comment).

I have swappedpyright forbasedpyright as you described but it happened again.

Here are some more observations:

1. It is broken for the current buffer only, switching to another buffer works as usual.
2. RunningLspInfo on both buffers shows 0 difference (I copied and diff'ed)
3. :verbose nmap gr shows a difference:

> n  gr          *@<Cmd>FzfLua lsp_references      jump1=true ignore_current_line=true<CR>>                  References

4. :verbose nmap gd also shows a difference:

No mapping found (obviously in the buffer that doesn't work)

vs

n  gd          *@<Cmd>FzfLua lsp_definitions     jump1=true ignore_current_line=true<CR>                 Goto Definition

5. Closing the buffer (bd) and reopening it, does not fix it.
6. It happens on freshly opened buffers.

@dpetka2001 ran fresh installation - as you described, only thing I installed afterwards islang.python fromLazyExtras and it did happen again:

gr

LspRestart fixed it.

I have kept the "lazytest" installation in case you want me to test something else.

If you or@folke want to jump on a call to do some live debugging, I am more than happy to!