You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS and Version: Linux x64 6.8.0-49-generic (Ubuntu 22.04.5 LTS)
VS Code Version: 1.95.3
C/C++ Extension Version: v1.22.11
ms-vscode.makefile-tools: v0.11.13
mesonbuild.mesonbuild: v1.26.0
Bug Summary and Steps to Reproduce
Bug Summary:
Unexpected C_Cpp.default.configurationProvider modification appear in C/C++: Log Diagnostics, although setting is not modified.
As a result, some files' intellisense is incorrect.
My project happens to have a broken meson.build file and valid autotools/makefile.
Ensure that C_Cpp.default.configurationProvider is always ms-vscode.makefile-tools.
Use vscode and run make/configure.
After some time, intellisense of some (newly opened or created) files went wrong.
Check C/C++: Log Diagnostics and find out that compiler/flags are wrong.
Further check C/C++: Log Diagnostics and find this:
However, this setting was never changed.
Check settings and command palette: setting is ms-vscode.makefile-tools.
In command palette: set configurationProvider to None then back to ms-vscode.makefile-tools. And the problem seems temporarily fixed:
Intellisense is back to normal, and mesonbuild.mesonbuild is gone from C/C++: Log Diagnostics.
Change makefile-tools version (and restart extension), or reload windows, also have a chance to trigger the unexpected Modified Settings.
Configuration and Logs
`C/C++: Log Diagnostics` is not persistent.
I don't know the exact condition to reproduce this issue (or if it is random).
Other Extensions
No response
Additional context
Expected Behavior:
If for some reason, ms-vscode.makefile-tools fails, actual C_Cpp.default.configurationProvider should fallback to None instead of an unpicked provider.
If actual C_Cpp.default.configurationProvider changed, an error/warning message should be presented to user.
ms-vscode.makefile-tools should not fail.
The text was updated successfully, but these errors were encountered:
Environment
Bug Summary and Steps to Reproduce
Bug Summary:
Unexpected
C_Cpp.default.configurationProvider
modification appear inC/C++: Log Diagnostics
, although setting is not modified.As a result, some files' intellisense is incorrect.
C_Cpp.default.configurationProvider
is alwaysms-vscode.makefile-tools
.Check
C/C++: Log Diagnostics
and find out that compiler/flags are wrong.Further check
C/C++: Log Diagnostics
and find this:Check settings and command palette: setting is
ms-vscode.makefile-tools
.None
then back toms-vscode.makefile-tools
. And the problem seems temporarily fixed:Intellisense is back to normal, and
mesonbuild.mesonbuild
is gone fromC/C++: Log Diagnostics
.Modified Settings
.Configuration and Logs
Other Extensions
No response
Additional context
Expected Behavior:
ms-vscode.makefile-tools
fails, actualC_Cpp.default.configurationProvider
should fallback toNone
instead of an unpicked provider.C_Cpp.default.configurationProvider
changed, an error/warning message should be presented to user.ms-vscode.makefile-tools
should not fail.The text was updated successfully, but these errors were encountered: