Task Explorer gets hung scanning for tasks on a newly cloned workspace.

[blu28]

Task Explorer gets hung scanning for tasks on a newly cloned workspace.

VScode 1.74.2 Task Explorer 2.13.2 Windows 10.

I clone a workspace from Github and select the option to open in a new window. If I select the Task Explorer panel, the icon displays a "watch" badge forever and doesn't show any tasks on the panel, it is empty. The status bar quickly shows the status as it scans various places, but once it stops it still shows the watch and no tasks. Rather unexpectedly, if I click the refresh button and then the "play" button, it will run the last task I ran before, even though it doesn't show anything.

If I exit VScode entirely and restart it, then Task Explorer displays the tasks just fine.

[JosunLP]

I experience i similar Issue, with i small difference. A restart won't fix the extension. It's permanently broken. I tried to reinstall it, even reinstall my VSCode. Nothing seams to work. It just starts to spin indefinitely again.

[mhdirkse]

I also have the issue that Task Explorer hangs, but in my case it is not about newly cloned directories. I am working with Windows 11 and Task Explorer plugin version v2.13.2.

When I clone https://github.com/ibissource/frank-manual, checkout commit 275c618c16d91e0b553e908d11bad9b7a0c4f20d and open VSCode in folder srcSteps/NewHorizons/v410 then Task Explorer hangs. It is true that there are no tasks to show, but I would expect the search for tasks to end. I would also expect that a line appears for the last ANT tasks, but it does not appear. I also tried to add some build.xml that works within another project, but the task defined does not appear.

When I clone https://github.com/ibissource/zaakbrug, checkout commit d558b48a91fba05402b8404977bd09cda8992e19 and open VSCode in that checkout directory, searching ends and I do see the ANT tasks defined in build.xml.

I repeated these steps for version v1.30.2 of the task explorer plugin with the same results.

Here are some screenshots of my settings for the task explorer plugin in VSCode:

[spmeesseman]

v3 may fix all of this, and is due out soon. once out, we can go from there