Tasks not running after update

[WardDurossette]

CopyCurrentFileToDev.txt

Issue Type: Bug

I have a task that copies the current editor window file to a remote file share. The output window is blank, the task does not seem to run, the destination does not contain the file. The attached file CopyCurrentFileToDev.txt is the .ps1 task, with a renamed extension.

VS Code version: Code - Insiders 1.36.0-insider (6520c22, 2019-06-19T05:19:10.147Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 x 3600)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software oop_rasterization: disabled_off protected_video_decode: enabled rasterization: enabled skia_deferred_display_list: disabled_off skia_renderer: disabled_off surface_synchronization: enabled_on video_decode: enabled viz_display_compositor: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	63.88GB (48.69GB free)
Process Argv
Screen Reader	no
VM	0%

Extensions (6)

Extension	Author (truncated)	Version
xml	Dot	2.5.0
gitlens	eam	9.8.2
mssql	ms-	1.6.0
csharp	ms-	1.20.0
powershell	ms-	2019.5.0
vscodeintellicode	Vis	1.1.7

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Tasks: Configure Task opens menu with one item (#40508)
• Change debugging tab to be tasks tab (#38969)
• Show task output automatically if there is only one task running (#73537)
• Terminate task: all running tasks polish (#73417)
• Proposal: Add "Run Task" context menu to any ".js" file containing a "# task" pragma comment (#1790)

[sarahkittyy]

I am also having this issue- after updating the insiders build, some tasks won't start. No output, no response at all.

[sarahkittyy]

I've managed to consistently reproduce it.

• VSCode Version:

1.36.0-insider
6520c22b83c0b6f168ba7de3309ffab42281e905
x64

• OS Version: 5.1.11-arch1-1-ARCH GNU/Linux

Current Behavior

Tasks run_notworking1 and run_notworking2 do nothing when run in the latest vscode-insiders version. No feedback, no output window, no error.
Task run_working does what's expected - prints 'Hello, World!' to the task output box.

Relevant Files

tasks.json

{
	// See https://go.microsoft.com/fwlink/?LinkId=733558
	// for the documentation about the tasks.json format
	"version": "2.0.0",
	"tasks": [
		{
			"type": "shell",
			"label": "run_notworking1",
			"command": "python",
			"args": [
				"Program.py"
			],
			"problemMatcher": []
		},
		{
			"type": "shell",
			"label": "run_notworking2",
			"command": "python ${relativeFile}",
			"problemMatcher": []		
		},
		{
			"type": "shell",
			"label": "run_working",
			"command": "python Program.py",
			"problemMatcher": []
		}
	]
}

Program.py

print('Hello, World!')

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

[alexr00]

@WardDurossette I used your task and made a ps1 file that just prints hello. The parameters are all passed in correctly:

Do you have any other repro steps?

[alexr00]

@sarahkittyy I also cannot reproduce what you're seeing. I tested on Windows and Ubuntu 18, and all three of your tasks worked for me. We don't have an official Arch Linux release, so I'm guessing there's something wrong with that.

[sarahkittyy]

Still not working after the latest update, even after clearing all settings and running with extensions disabled. It might be noted that I'm using fish as my default shell, though I don't know if it's relevant with settings cleared & some tasks working while others aren't.

1.36.0-insider
c3fe2d8acde04e579880413ae4622a1f551efdcc
x64

Video of this issue

[sarahkittyy]

Update: If I put the run_notworking1 or run_notworking2 tasks as the preLaunchTask in a launch.json debugger configuration, I get the same error as referenced in issue #75777.

.vscode/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": [
		{
			"name": "Python: Current File",
			"type": "python",
			"request": "launch",
			"program": "Program.py",
			"console": "integratedTerminal",
			"preLaunchTask": "run_notworking1"
		}
	]
}

Running the configuration:

[WardDurossette]

Yes, this task is not a new task - I used this for months and months maybe even a year? it's worked perfectly until the last update of VSCode Insiders - The task itself copies the file I have open (in focus) in VSCode out to the WWW root folder of my development web server, including sub-paths. Very handy to shorten my development cycle - edit, save, F1/Run Task, refresh the browser. The weird thing is that the output / tasks window is completely blank. There has to be an getting thrown somewhere, not familiar enough to know where.

…

On Thu, Jun 20, 2019 at 2:59 AM Alex Ross ***@***.***> wrote: @WardDurossette <https://github.com/WardDurossette> I used your task and made a ps1 file that just prints hello. The parameters are all passed in correctly: [image: image] <https://user-images.githubusercontent.com/38270282/59831307-d360bb00-9341-11e9-80da-acc733243160.png> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#75774?email_source=notifications&email_token=AEW2CNETLBOIKMK3Q6TMNR3P3M2HFA5CNFSM4HZJ4TBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYETMZY#issuecomment-503920231>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEW2CNEE6XD7RGDUZQXR3QLP3M2HFANCNFSM4HZJ4TBA> .

-- Ward Durossette

[WardDurossette]

@WardDurossette I used your task and made a ps1 file that just prints hello. The parameters are all passed in correctly:

Do you have any other repro steps?
@alexr00

So the terminal window displayed at the bottom of your screenshot is not what I see. I used to see that.
But now when I "F1" "Run Task", and then select my task from the drop down list, I don't have a "1: Task - " in my drop down terminal window choices. I edited my task to just output a "Hello World" as the first line, commenting out all the rest, and no output was given.

Even the output in your screenshot where you see "> Executing task:" that's not there.

I looked in the "C:\Users\rdurossette\AppData\Roaming\Visual Studio Code - Insiders\logs" but there are not any files there.

[wbuck]

I'm seeing the same issue with version 1.36.0-insider.
I have some custom tasks for running makefile targets which have been working for weeks which are no longer working. When I attempt to run them via my custom key bindings or from the command palette nothing happens. I should note though that the default build task still works, but my custom rebuild and clean tasks do nothing.

[alexr00]

I still can't reproduce any of this, but I have a guess about which change caused the issue. I have pushed a potential fix.

Please everyone in this thread update to the next version of VS Code insiders when it release (it will be the version after 9ff8ae0 and have a date after Jun 21). I will add the commit number of the insiders build here, but you might see the update before I can add it here.

[sarahkittyy]

I am waiting for the update but I decided to test a little more and it might have something to do with the shell?
If I create a new task:

"tasks": [
		{ // Previously this task wouldn't provide any output at all, now I've added the "options" section
			"type": "shell",
			"label": "run_kindaworking",
			"command": "python",
			"args": [
				"Program.py"
			],
			"options": {
				"shell": {
					"executable": "/bin/bash" //Default shell for me is /usr/bin/fish
				}
			},
			"problemMatcher": []
		}
]

Instead of nothing being outputted / shown at all, I now see this:

Setting the shell to /usr/bin/fish simply does nothing- vscode gives no feedback whatsoever.

Also, in the image above, it seems that the command & args are wrapped in single quotes -- it's trying to launch /bin/bash 'python Program.py' which isn't valid anyway. If I set the "executable" parameter in options.shell to /bin/bash -c I again get absolutely no feedback whatsoever.

[yanghanlin]

I have received and installed the update.

This time tasks cannot still be executed; there appears a error message that reads Cannot read property 'strong' as undefined. I opened the developer tools and collected the output of the console into
this log file. It seems another internal error.

[alexr00]

Thank you @yanghanlin, that is very helpful! I'm not sure how it could have happened, but I think we are detecting your platform incorrectly. Would you be able to set a couple breakpoints? You should be able to open the developer tools, go to the sources tab, and ctrl+p to find the file.

This one happens when you reload VS Code. I am curious if _isNative gets set in this if statement. https://github.com/Microsoft/vscode/blob/master/src/vs/base/common/platform.ts#L50

This one will hit when you try to run a task. What is the value of the platform argument?
https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/contrib/tasks/browser/terminalTaskSystem.ts#L1123

[sarahkittyy]

I am also experiencing the same error: Cannot read property 'strong' of undefined

1.36.0-insider
6a7020dd4a11e0f33b157b3df4baeec90d85701b
x64

uname -a
# Linux sarahkitty 5.1.12-arch1-1-ARCH #1 SMP PREEMPT Wed Jun 19 09:16:00 UTC 2019 x86_64 GNU/Linux

The window log gives this trace:

[2019-06-24 11:00:04.990] [renderer1] [error] Cannot read property 'strong' of undefined: TypeError: Cannot read property 'strong' of undefined
    at l (file:///opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.main.js:3162:703)
    at d (file:///opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.main.js:3163:444)
    at x.buildShellCommandLine (file:///opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.main.js:3163:662)
    at x.<anonymous> (file:///opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.main.js:3158:611)
    at Generator.next (<anonymous>)
    at r (file:///opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.main.js:35:293)
    at process._tickCallback (internal/process/next_tick.js:68:7)

[wbuck]

I'm also experiencing the "Cannot read property 'strong' of undefined". I can attempt to debug after work tonight.

[yanghanlin]

@alexr00 I have set the breakpoints according to your instruction, and here is what I find:

(I'm sorry that I am not familiar with front-end development, therefore I may have done it incorrectly)

The first breakpoint

I set the first breakpoint in Line 50 of platform.ts and found that, as VSCode hit the breakpoint on reloading, the variable _isNative was false.

Then I stepped through the if block, and when the program finally got through the block, it could be seen that _isNative had been set to true.

The second breakpoint

When the second breakpoint was hit, it could be seen that the value of the platform argument was 3.

[wbuck]

I should also note that I'm launching VSCode from my Ubuntu WSL distro.

[yanghanlin]

I have also launched VSCode from my Ubuntu WSL (Version 1) distro for several times to try out VSCode Remote when it was released. However, I was not using it when the problem occurred.

[alexr00]

Thank you for your help! I now see the problem and I've pushed a fix. It will be in the next insiders!

[sarahkittyy]

Can confirm it's fixed in version 41691474e5fa22a279d49fc4b58af66bc11ce41b

[wbuck]

My tasks are correctly running again after update. Thanks

[yanghanlin]

Everything works perfectly now. Thank you!

[alexr00]

Thank you all for verifying!

[nicolas-oliveira]

I can't run tasks in 1.36.1 Manjaro/Arch Linux
I downgraded to 1.30.2 and everything goes fine
This is the task:

{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "debug",
            "type": "shell",
            "command": "",
            "args": [
                "g++",
                "-g",
                "${relativeFile}",
                "-o",
                "a.exe"
            ]
        },
        {
            "label": "Compile and run",
            "type": "shell",
            "command": "",
            "args": [
                "g++",
                "-g",
                "${relativeFile}",
                "-o",
                "${fileBasenameNoExtension}.out",
                "&&",
                "clear",
                "&&",
                "./${fileBasenameNoExtension}.out"
            ],
            "group": {
                "kind": "build",
                "isDefault": true
            },
            "problemMatcher": {
                "owner": "cpp",
                "fileLocation": [
                    "relative",
                    "${workspaceRoot}"
                ],
                "pattern": {
                    "regexp": "^(.*):(\\d+):(\\d+):\\s+(warning|error):\\s+(.*)$",
                    "file": 1,
                    "line": 2,
                    "column": 3,
                    "severity": 4,
                    "message": 5
                }
            }
        }
    ]
}

[alexr00]

@NickCageNick this is, sadly, expected right now. When 1.37.0 release you will have the fix. Or, you can try insiders and get the fix now.