bug: no breakpoint indication sign

[verajosemanuel]

Did you check docs and existing issues?

• [X] I have read all the LazyVim docs
• [X] I have searched the existing issues of LazyVim
• [X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

v0.10.0-dev

Operating system/version

Ubuntu WSL2

Describe the bug

Breakpoint symbols does not appear when inserted. Debug worked , but no visual indication of the breakpoints.

Checked this closed issue for fixes, to no avail. https://github.com/LazyVim/LazyVim/issues/2147

Steps To Reproduce

1. install neovim nightly
2. install lazyvim
3. install needed plugins for debugging python (Mason, Extras...)
4. Open a python file, insert a breakpoint and debug

Expected Behavior

Expected is to have visual icons to indicate where breakpoints are placed.

Repro

No modifications done. Just plain simple Lazyvim starter template.

[dpetka2001]

Something changed with the priority of debugging icons. I don't know if that comes from debugpy itself or somewhere else. Essentially the LazyVim statuscolumn shows icons based on priorities. It will always show the highest priority icon (i.e the LSP error icon always has higher priority than some other icon). Since the icons appear in the same column (left from the numbers) only one will appear at the same time. That's how Lazyvim statuscolumn operates.

This is how it looks for me. The yellow arrow that shows the point you're at didn't use to be there (either it didn't exist or it had lower priority than the debugging icon). There's not much from LazyVim side to be done about this, because in the next line you can see the second breakpoint that I set appear correctly.

[verajosemanuel]

Hi @dpetka2001 I have copied your code but still not seeing the icons; I have added two breakpoints., one for each print inside the function.

[dpetka2001]

Can you try with a fresh LazyVim starter template

1. `mkdir ~/.config/lazytest`
2. `git clone https://github.com/LazyVim/starter ~/.config/lazytest`
3. `NVIM_APPNAME=lazytest nvim` and wait for the installation to complete
4. Restart Neovim with the command provided in step 3 and install from `:LazyExtras` only `lang.python` and `dap.core`
5. Restart Neovim with command from step 3 and set breakpoints in a python file like you said

Do you observe the same behavior?

For cleanup

rm -rf ~/.config/lazytest
rm -rf ~/.local/share/lazytest
rm -rf ~/.local/state/lazytest
rm -rf ~/.cache/lazytest

[verajosemanuel]

Done, testing confirmed the issue. Breakpoint icons are not present with this bare minimum install.

In addition, when debugging i get an error that is not present when working with my original nvim:

../.local/share/lazytest/lazy/nvim-dap/lua/dap/session.lua:1420: Error running /home/joe/.local/share/lazytest/mason/packages/debugpy/venv/bin/python: ENOENT: no such file or directory

[dpetka2001]

What are the contents of ~/.local/share/lazytest/mason/packages/debugpy/venv/bin/ directory?

[dpetka2001]

I just noticed that you're using WSL. Do you happen to have a bare Linux OS where you can test if the same behavior occurs?

[verajosemanuel]

folder contents:

My old laptop with ubuntu 22.0.4 and neovim 0.9.5 worked ok

seems to be WSL2 specific or Neovim 0.10 specific

[verajosemanuel]

I performed a New test on a different machine: a desktop computer with Windows 11, Ubuntu WSL2. Neovim 0.10 Same results, seems to be an issue related to WSL2 and Neovim 0.10

[dpetka2001]

Can you test with Neovim 0.9.5 in your WSL Ubuntu?

[verajosemanuel]

Hi @dpetka2001 , managed to install bob neovim version manager and tested with version 0.9.5 Icons a bit small but ok. Definitely is a 0.10 issue.

[dpetka2001]

Did you previously install 0.10 via bob as well? If not, pls could you also try with Neovim nightly installed via bob? It could be just a package thing about how Neovim was built from the source that you used to install it.

[verajosemanuel]

confirmed. No matter the way you install neovim. If version is 0.10 and WSL2: no breakpoint signs

[pschwartz]

I think there is something going on beyond 0.10.0 on WSL2. I am running the latest LazyVim on MacOS Sonoma 14.3 and seeing the same issue with both the brew installed current release which is 0.9.5 and with the brew --head release which is the nightly of 0.10.0.

It is worth noting that before moving this week to LazyVim, using a hand rolled set of configs, the identifiers in the gutter were working without an issue.

[weberam2]

Not sure what's it's worth, but I am experiencing the same issue. Running Ubuntu 22.04 Nvim 0.10.0-dev-777 LazyVim 10.12.0

With my NVChad setup, I do see the Breakpoint...

[wikiliu]

And I did`t see any diagnostics icon in neovim0.9.5 + arch-wsl , maybe is a same problem as above. If I only open a single c-file, all statuscolumn icon are ok

[wikiliu]

And I did`t see any diagnostics icon in neovim0.9.5 + arch-wsl , maybe is a same problem as above. If I only open a single c-file, all statuscolumn icon are ok

fixed by: https://github.com/LazyVim/LazyVim/issues/1035

[weberam2]

This did not fix it for me...

[folke]

I can't reproduce this. In the buffer where the signs don't show, what does :verbose set signcolumn show?

[folke]

Can you also try this work-around? https://github.com/LazyVim/LazyVim/issues/1035#issuecomment-1634246293

If the output was yes, and the work-around works, then it's probably that the signcolumn doesn't get updated when needed in Neovim 0.10.0