-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
The task provider for "C/C++" tasks unexpectedly provided a task of type "shell". #5388
Comments
Similar behavior here with ROS
This is there since one of the last Insider updates. My version
|
reverting to 0.27.1 fix problem |
Same issue for me on macOS Version: 1.45.0-insider |
Same issue on macOS. macOS Catalina 10.15.5 |
facing a similar kind of issue on 0.28 Insiders version as well as 0.27.1 version. Edit: with all versions. Version: 1.45.0-insider (user setup) |
If I run task instead of build task, the issue will not appear. |
Same issue for me, Version: 1.45.0-insider (system setup) but it will not appear on my vscode stable. Version: 1.44.2 (system setup) |
@Primimy If the bug occurs on 1.45-insiders but not 1.44.2 (both with 0.28.0-insiders2) then that suggests it's a VS Code bug and not a bug with out C/C++ extension. |
In this extension's call to vscode-cpptools/Extension/src/LanguageServer/extension.ts Lines 174 to 180 in ef120e8
However, then it provides tasks of type shell not of type C\C++ , which is unexpected. It used to work because VS Code was just blindly accepting all tasks. With the recent changes to the task quick pick to make it faster, it can't do that. I added this error message recently so that folks would notice this problem.
The quickest and most correct way for this extension to stop having this error would be to provide tasks of type
That said, I'll make a small change to not show the notification in this case. Then, I'll see what can be done about the task not showing in the "recent" section. |
+1.
|
+1, same issue for macOS 10.14.4, after update VSCode to 1.45.0. Version: 1.45.0 |
+1 Same issue on Windows 10 after update 1.45.0 Version: 1.45.0 (user setup) |
The same problem for me.
|
+1 Same issue on Windows 10 after the new update Version: 1.45.0 (user setup) |
Same here with the meson build extension |
Change C/C++ taskSourceStr to shell. Fixes #5388
We have a fix with https://github.com/microsoft/vscode-cpptools/releases/tag/0.28.0-insiders3 . We plan to release 0.28.0 on Monday (or maybe Tuesday). |
Thank you for the quick fix. Installed 0.28.0-insiders3. Issue resolved.
|
Good job,thank you. |
Nice. But the terminal always displays the Look like this: I remember it didn’t appear before. It is a bug? |
@Gorgeous2017 It did appear before. It's basically similar to "press any key to continue" |
|
Actually, if you don't configure a right path for gdb, this error will occur. |
What if I'm not using GDB? I use MS C++. |
For those having hard time figuring this out,
|
+1 Same problem here. |
Thanks muhammad-osaid-tekfocal, it works like a charm! :) |
is it okay to revert back to default update channel after updating? |
It's OK to revert back to the default Update Channel after installing the insiders release. The insider version will remain until a newer official release is available on the default Channel.
|
@ayams02 We had a bug that prevented auto-downgrading from 0.28.0-insiders3 to 0.27.1 when the updateChannel changes to "Default" (#5464), but that should be fixed for future Insider releases...and we should be releasing 0.28.0 soon anyway. |
Yoo-hoo! Platformio now reports it has 0.28.0 installed. @sean-mcmanus, Thank You.
|
As of about an hour ago I have 0.28.0 installed and the issue is gone. |
The default template of launch.json and task.json may be not correct as before. I generate many times to get the fine version to debug like before. I don't why, but this is the truth. Wish you could find out the real problem which causes this error. Thanks. |
VSCode version:
vscode-cpptools version:
0.28.0-insiders
Here is my
tasks.json
.If I change my code, or otherwise sometimes completely randomly, when I run task
run
, I get this message:And when I hit, "Show output" I see:
Is something wrong with my
tasks.json
? I can't replicate this consistently? This does not happen when all extensions are disabled.The text was updated successfully, but these errors were encountered: