Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Diagnostic failure #462

Closed
sidlatau opened this issue Oct 11, 2024 · 0 comments · Fixed by #463
Closed

[BUG] Diagnostic failure #462

sidlatau opened this issue Oct 11, 2024 · 0 comments · Fixed by #463
Assignees

Comments

@sidlatau
Copy link
Contributor

NeoVim Version
NVIM v0.11.0-dev-6292+g58406ab9f0-Homebrew
Build type: Release
LuaJIT 2.1.1727870382
Run "nvim -V1 -v" for more info

Describe the bug
Sometimes diagnostic fails:

neotest-dart: /Users/ts/.local/share/nvim/lazy/nvim-nio/lua/nio/init.lua:119: The coroutine failed with this message:                                
/Users/ts/.local/share/nvim/lazy/nvim-nio/lua/nio/tasks.lua:100: Async task failed without callback: The coroutine failed with this message:         
...ub/personal/neotest/lua/neotest/consumers/diagnostic.lua:88: attempt to index a nil value                                                         
stack traceback:                                                                                                                                     
        ...ub/personal/neotest/lua/neotest/consumers/diagnostic.lua: in function 'create_diagnostics'                                                
        ...ub/personal/neotest/lua/neotest/consumers/diagnostic.lua:54: in function 'draw_buffer'                                                    
        ...ub/personal/neotest/lua/neotest/consumers/diagnostic.lua:177: in function 'draw_buffer'                                                   
        ...ub/personal/neotest/lua/neotest/consumers/diagnostic.lua:239: in function 'listener'    

Expected behavior
Setting diagnostic should not crash tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants