Breakpoint is not hit (neotest, neotest-golang, nio, async) #84
Unanswered
ruslanSorokin
asked this question in
Q&A
Replies: 1 comment 9 replies
-
|
Is it possible that the breakpoint is placed in a "fast" event callback This can be checked by calling And another question, I see that the breakpoint is placed on different lines ( in the case where it hits and where it doesn't ). Is it a random behaviour or does it depend on the line where you put the breakpoint ? |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've read the disclaimer about fs paths and double-checked that the filepath is correct and none of the directories in the path are symlinked. I've also confirmed via both tracing and
vim.printthat the line is being executed.I've tried to run the code triggering the line
require("neotest").run.run()wrapped inrequire("nio").run(require("neotest").run.run().wait)but it didn't seem to help.This is the clean log file where I successfully hit the breakpoint:
And this is the log where the breakpoint isn’t hit:
(PS: I think I forgot to wait until I had closed Neovim, so there is no ‘SERVER TERMINATED’ log entry. Just in case somebody assumes that Neovim is frozen and I had to kill the process and that is why there is no 'SERVER TERMINATED' - this is not true; code is still being executed like no debugger is attached)
Beta Was this translation helpful? Give feedback.
All reactions