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
Is it intended that the debug aborts when the preLaunchTask fails? I'm seeing the correct behavior out of overseer when my preLaunchTask (a build of my C++ project) fails, so it seems to be interpreting the failure/success of the preLaunchTask successfully. However, dap doesn't seem to care and launch regardless.
Overseer lua config:
require('overseer').setup({
component_aliases= {
-- Most tasks are initialized with the default componentsdefault= {
{ 'display_duration', detail_level=2 },
'on_output_summarize',
'on_exit_set_status',
{
'on_complete_dispose',
statuses= {},
require_view= { 'SUCCESS' },
},
},
-- Tasks from tasks.json use these componentsdefault_vscode= {
'default',
'on_result_diagnostics',
{
'open_output',
direction='float',
on_complete='failure',
on_start='never',
focus=true,
},
},
},
})
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Is it intended that the debug aborts when the preLaunchTask fails? I'm seeing the correct behavior out of overseer when my preLaunchTask (a build of my C++ project) fails, so it seems to be interpreting the failure/success of the preLaunchTask successfully. However, dap doesn't seem to care and launch regardless.
Overseer lua config:
.vscode/launch.json
.vscode/tasks.json
Beta Was this translation helpful? Give feedback.
All reactions