In VSCode, when using Copilot with C++ code but C_Cpp.intelliSenseEngine is disabled, it shows a warning popup but it still works

[egrosspietsch-fds]

Select Topic Area

Bug

Body

We are using the clangd extension for C++ because its Intellisense-capabilities work better on our large codebase. However, we use MSFT's C/C++ extension for debugging.

When we have the Copilot extension enabled, if I start typing code it pops up a warning "IntelliSense-related commands cannot be executed when 'C_Cpp.intelliSenseEngine' is set to 'disabled'".

If I disable the Copilot extension, the warning is not displayed.

Despite this warning, as far as I can tell Copilot seems to be working - it displays suggestions that I can tab-complete, and Ctrl+i works for chat.

I see that there is an option to disable ALL info/warning messages from the C/C++ extension, but since we still using it for debugging I don't want to do that.

This message is displayed the first time you type code in a window, and displayed again every time you reload the window.

I know that Copilot didn't always do this, so I went back and installed previous versions of the Github Copilot extension and found when the warning started showing up:

v1.186.0 (and later versions) - does cause this warning popup
v1.184.0 - does NOT cause this warning popup
(I don't know what happened to v1.185, VSCode doesn't present me an option to install it)

I've tried both VSCode 1.90.2 and 1.91.1 and it happens in both.

I set the log level to 'Trace', but do not see anything interesting in the Output of the "Github Copilot" or "C/C++" extensions. I do see this in the "Extension Host (Remote)" Logs when the error is encountered:

[trace] ExtHostCommands#executeCommand C_Cpp.getIncludes

I assume Copilot is the extension trying to call the C_Cpp.getIncludes command from the C/C++ extension, which is causing the warning to be thrown. However, since Copilot still works, it is an annoyance to have the popup in every window. Perhaps Copilot could check that C_Cpp.intelliSenseEngine is enabled before calling this command?

Version: 1.91.1 (user setup)
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:06:49.809Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.22631

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[benmcmorran]

Thanks for reporting this! I've opened a PR with a fix in the cpptools repo.

[egrosspietsch-fds]

Thanks!