Closed prdanelli closed 2 years ago
I noticed this the other day and a nice diagnostic = false
in the config fixes the issue ๐ .
Seriously though I'm not sure what is causing the duplicates. If you restart Neovim and run lua require("neotest").run.run()
next to that troublesome test can you confirm how many items get sent to Trouble?
I can confirm that after the restart, with Trouble empty before, running the failing test fills it with multiple duplicates - 92 of them. And diagnostic = false
prevents them from showing.
Before...
After...
Hahaha wow. 92!
I'll have to do some digging into how neotest
handles this in order to solve!
I too was surprised by the shear volume of messages :D
Figured out the error. Because I'm passing the whole backtrace to the error block!
That's more like it:
I'll format the output soon
Hopefully should be more readable:
OMG your bottom bar is beautiful! I wanted to ask you how you got the line-height on it, as I couldn't see anything in your dotfiles that worked for me?
It should be this line in my kitty.conf
. It's only taken me about 1,000 hours to get it just how I like it ๐ .
Thank you! I tried it out and it ...
I might have to adjust it slowly over time to get used to it :D
It's getting closer to a banana than an apple ๐ . Mine looks the same unfortunately.
I'm edging you in the brew packages stakes though:
Hello,
I'm not sure if this is an issue, one that related to this adapter or Neotest, but I thought I would mention it anyway.
When I run a set of specs, I see a non-uniq list of failures being populated into the LSP Diagnostics quicklist LSP plugin Trouble.
I've run these specs a few times now (as I am not managing to fix the issue ๐ค), but apart from that I can't think of a reason they would show in there like this.