Debug proceeds even if preLaunchTask fails

[georgev93]

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 components
        default = {
          { '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 components
        default_vscode = {
          'default',
          'on_result_diagnostics',
          {
            'open_output',
            direction = 'float',
            on_complete = 'failure',
            on_start = 'never',
            focus = true,
          },
        },
      },
    })

.vscode/launch.json

    "version": "0.2.0",
    "configurations": [
        {
            "type": "codelldb",
            "request": "launch",
            "name": "vsc_Debug",
            "preLaunchTask": "ninja_build_test",
            "program": "${workspaceFolder}/build/tests",
            "args": [],
            "cwd": "${workspaceFolder}"
        }
    ]

.vscode/tasks.json

        {
            "label": "ninja_build_test",
            "type": "shell",
            "presentation": {
                "echo": false,
                "reveal": "silent",
                "focus": true,
                "panel": "new",
                "showReuseMessage": false,
                "clear": false
            },
            "linux": {
                "command": "ninja tests -C build"
            },
            "windows": {
                "command": "ninja tests.exe -C build"
            }
        },

[georgev93]

Disregard! This was behavior from the overseer.nvim plugin (Related discussion here)