Thanks to visit codestin.com
Credit goes to github.com

Skip to content

errors in dependsOn background tasks do not prevent subsequent tasks from executing #70283

@pandorla1984

Description

@pandorla1984
  • VSCode Version: 1.32.1
  • OS Version: 18309

Steps to Reproduce:

create launch.json:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [        
        {
            "type": "chrome",
            "request": "launch",
            "name": "Launch Chrome against localhost",
            "url": "http://localhost:8080",
            "webRoot": "${workspaceFolder}\\src\\FrontEnd\\build",
            "preLaunchTask": "core"
        }
    ]
}
  1. create task.json:
{
    // See https://go.microsoft.com/fwlink/?LinkId=733558 
    // for the documentation about the tasks.json format
    "version": "2.0.0",
    "tasks": [
        {
            "label": "core",            
            "type": "npm",
            "script": "start",
            "path": "src/FrontEnd/core/",
            "isBackground": true,
            "dependsOn":["loss"],
            "problemMatcher":{
                "owner": "custom",
                "pattern":[
                    {
                        "regexp": "something not exists",
                        "file": 1,
                        "location": 2,
                        "message": 3
                    }
                ],
                "background": {
                    "activeOnStart": true,
                    "beginsPattern": "[email protected] start",
                    "endsPattern": "created ..\\\\build\\\\vendor.js"
                }
            }
        },
        {
            "label": "loss",            
            "type": "npm",
            "script": "watch",
            "path": "src/FrontEnd/loss/",
            "isBackground": true,            
            "problemMatcher":{
                "owner": "custom",
                "pattern":[
                    {
                        "regexp": "something not exists",
                        "file": 1,
                        "location": 2,
                        "message": 3
                    }
                ],
                "background": {
                    "activeOnStart": true,
                    "beginsPattern": "[email protected] start",
                    "endsPattern": "waiting for changes"
                }
            }
        }
    ]
}

I can use beginsPattern/endsPattern with no issue if I direct launched by preLaunchTask, but if I have DependsOn for same task, it will run the dependencies but can't detect it's status by using endsPattern, the task will hang there. it looks like a bug for me.

I tried to use the new Terminal: "terminal.integrated.windowsEnableConpty": false/true, no difference.
I tried to use presentation.panel:"dedicated", no difference.

I think we have done a nice work on putting tasks running in background and launch, but not those tasks in DependsOn property.

Does this issue occur when all extensions are disabled?: Yes

Metadata

Metadata

Assignees

Labels

feature-requestRequest for new features or functionalitytasksTask system issues

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions