Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tasks: possible to run multiple of the same task -> broken terminal dropdown #35048

Closed
isidorn opened this issue Sep 26, 2017 · 10 comments
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug tasks Task system issues verified Verification succeeded
Milestone

Comments

@isidorn
Copy link
Contributor

isidorn commented Sep 26, 2017

Refs: #34953

  1. Follow the test plan, run the watch task in a multi folder workspace
  2. Delete that entry from tasks.json, run that task again
  3. Notice you have two of the same tasks running now (which you are prohibitin in other places)
  4. Now terminate one of those tasks, with the task: terminate action (terminate the second one if the first one is shown in the terminal)
  5. Notice the terminal dropdown becomes blank and looks broken

There might be some other breakage with having two of the same tasks running, this is the one I noticed.

screen shot 2017-09-26 at 11 57 29

@vscodebot vscodebot bot added the tasks Task system issues label Sep 26, 2017
@isidorn isidorn added the bug Issue identified by VS Code Team member as probable bug label Sep 26, 2017
@dbaeumer
Copy link
Member

This is not related to multi workspace setups. The problem is that deleting the task from the tasks.json file make the contributed task the primary task and hence it will not match the already running task. Need to see how to better compare them.

@dbaeumer dbaeumer added this to the September 2017 milestone Sep 27, 2017
@dbaeumer
Copy link
Member

Will investigate the broken terminal drop down for September since it is annoying.

@dbaeumer
Copy link
Member

Can't reproduce with a gulp watch task. Need to test npm

@dbaeumer
Copy link
Member

Ok. Was able to reproduce this with npm watch task as described in the test plan but I am not able to reproduce the empty drop down. Could this be the old drop down not initializing problem?

Here is what I see:

capture

@isidorn can you reproduce this if you opened the drop down before running any tasks ?

@isidorn
Copy link
Contributor Author

isidorn commented Sep 29, 2017

@dbaeumer now when following the exact steps from above I get a Cannot read property 'toString' of undefined
Here's where it explodes:

screen shot 2017-09-29 at 12 55 38

@isidorn isidorn reopened this Sep 29, 2017
@dbaeumer
Copy link
Member

Already fixed by: 2e4b6ce

@isidorn
Copy link
Contributor Author

isidorn commented Sep 29, 2017

I agree that the null exception is fixed, just verified, however I still get the broken terminal dropdown following the exact steps from my first comment.
Reopening.
IMHO this is not critical for September.

@isidorn isidorn reopened this Sep 29, 2017
@dbaeumer
Copy link
Member

@isidorn good catch. I thought since you can't run twice the problem doesn't show up again. But two tasks can be named twice.

@dbaeumer dbaeumer modified the milestones: September 2017, October 2017 Sep 29, 2017
@dbaeumer
Copy link
Member

Got fixed by having a qualified name in the task drop down.

@isidorn
Copy link
Contributor Author

isidorn commented Nov 2, 2017

Verified that the names are now qualified in the task drop down

@isidorn isidorn added the verified Verification succeeded label Nov 2, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 11, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug tasks Task system issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

2 participants