You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After running a failing job that correctly sets diagnostics, a second successful job does not clear out the diagnostics. Re running the initial failing job does reset the diagnostics.
IMO, this is surprising and requires scripting to workaround, which could ideally be handled by the components. Maybe this is a bug with on_result_diagnostics_quickfix.set_empty_results = true or user error.
PS.
Apologise for the minimal detail in the bug report, I'll try to follow up with some more screenshots / better reproduction steps.
What is the severity of this bug?
breaking (some functionality is broken)
Steps To Reproduce
Using the job component configuration below, with code that won't compile.
Running a 1st build job (error) correctly sets quickfix list and diagnostics
Fix the compilation issue
Running a 2nd build job (success) will not clear out the existing diagnostics.
(Re-running the 1st failed job - does clear out diagnostics)
Expected Behavior
on_result_diagnostics_quickfix.set_empty_result should clear out the diagnostics of a previous job
Minimal example file
No response
Minimal init.lua
return {
"stevearc/overseer.nvim",
config=function()
localoverseer=require("overseer")
overseer.setup({
-- Aliases for bundles of components. Redefine the builtins, or create your own.component_aliases= {
-- Most tasks are initialized with the default componentsdefault= {
{ "display_duration", detail_level=2 },
"on_output_summarize",
"on_exit_set_status",
"on_complete_notify",
"on_complete_dispose",
{ "on_output_quickfix", open_on_match=true, items_only=true, set_diagnostics=true },
{ "on_result_diagnostics", remove_on_restart=true },
{ "on_result_diagnostics_quickfix", set_empty_results=true },
},
},
})
end,
}
##Examplejobconfig```yamlon_output_quickfix (Setalltaskoutputintothequickfix (oncomplete))
close: falseopen: falsetail: trueerrorformat: %f:%l:%c: error: %mitems_only: trueset_diagnostics: trueopen_on_exit: neveropen_on_match: trueon_result_diagnostics (Iftaskresultcontainsdiagnostics, displaythem)
remove_on_restart: trueon_result_diagnostics_quickfix (Iftaskresultcontainsdiagnostics, addthemtothequickfix)
close: falseopen: falseuse_loclist: falseset_empty_results: trueResult:
diagnostics= {}
Additional context
No response
The text was updated successfully, but these errors were encountered:
#!/bin/bashecho'lua/overseer/init.lua:22: error: this is an error'echo'lua/overseer/init.lua:44: error: this is an error'# echo "success"
I run the task once, see the quickfix populated, comment/uncomment the quick.sh script to have it output no errors, then run a new task. The quickfix gets cleared for me.
Can you provide a minimal configuration that reproduces the issue?
Neovim version (nvim -v)
NVIM v0.9.5 Build type: Release LuaJIT 2.1.1703358377
Operating system/version
MacOS 14.4 (23E214)
Describe the bug
👋 thanks for the great plugin!
After running a failing job that correctly sets diagnostics, a second successful job does not clear out the diagnostics. Re running the initial failing job does reset the diagnostics.
IMO, this is surprising and requires scripting to workaround, which could ideally be handled by the components. Maybe this is a bug with
on_result_diagnostics_quickfix.set_empty_results = true
or user error.PS.
Apologise for the minimal detail in the bug report, I'll try to follow up with some more screenshots / better reproduction steps.
What is the severity of this bug?
breaking (some functionality is broken)
Steps To Reproduce
Expected Behavior
on_result_diagnostics_quickfix.set_empty_result
should clear out the diagnostics of a previous jobMinimal example file
No response
Minimal init.lua
Additional context
No response
The text was updated successfully, but these errors were encountered: