Closed hahuang65 closed 1 year ago
any updates on this issue? maybe there some workaround to disable that output?
Just so people don't waste lots of time expecting someone else to swoop in, there is no maintainer for this project. I got it up and running, but it works entirely on user contributions I'm not even working with go currently, so some other invested party will need to investigate and raise a PR 🙏🏿
@hahuang65 Could you please provide more details? Where that output comes from? What are a setup and steps to reproduce? From your description it is unclear what is issue about.
@RomanMelnyk113 if you can provide any details it would be helpful
@sergii4 thanks for following up on this... This happens when I run require("neotest").run.run(vim.fn.expand("%"))
and my cursor is on a line for a sub-test:
If I'm on a blank line, or the actual function for the test, the output is saner, but still somewhat un-useful:
While on the test function, the output will show the error:
Thanks, @hahuang65! I will take a look on weekend.
@hahuang65 I was trying to reproduce the bug, I put cursor on subtest line and executed:
:lua require("neotest").run.run(vim.fn.expand("%"))
output seems pretty regular to me
@sergii4 hmm this must be something specific to my project, as I've just created a throwaway package and I'm not running into this issue.
I did get 5 :+1: on my initial issue, and @RomanMelnyk113 also seems to run into this. I wonder if anyone knows how to reproduce it.
I'll poke around my project and try to see if I can figure out what is going on.
@sergii4 thank you for taking the time to look into this so far!
Hello @hahuang65 @sergii4 and thanks for looking into this problem!
yeah, I'm also having this when running (doesn't matter where cursor is)
:lua require("neotest").run.run(vim.fn.expand("%"))
But the problem is only for floating output window
:lua require("neotest").output.open({ enter = true, last_run = true })
And it shows okay when using output_panel
:lua require("neotest").output_panel.toggle({ last_run = true, enter = true })
It also worth to mention that this problem doesn't appear when running single test with following command
:lua require("neotest").run.run()
P.S. my guess this is something goes wrong here https://github.com/nvim-neotest/neotest-go/blob/45737334fe8f0e9df4848865d11f70c49956baca/lua/neotest-go/output.lua#L45
Hi @hahuang65 @RomanMelnyk113, I reproduced issue with:
:lua require("neotest").output.open({ enter = true })
and even with:
:lua require("neotest").output.open({ })
Thank for a hint :) . I keep looking
I have found the problem. Fix is coming
@RomanMelnyk113 @hahuang65 neotest provides test output regarding nearest test position to cursor, for ex., nested test:
function level test:
But there is problem on the file level
@hahuang65 @RomanMelnyk113 could you please update the neotest-go and check if issue still reproduces?
@sergii4 looks good to me.
@hahuang65 thanks, I am closing it then.
When I run a file in Go, the test output is difficult to read: