Open ahtotruu opened 1 year ago
Thanks for the report!
The C/C++ Extension Pack is indeed not installed -- it contains C/C++ Themes
and CMake Tools
besides the one extension which is installed in the VM: C/C++
.
I think neither of the not-installed project has any importance for single-file projects. So I see thus prompt as annoyance. (maybe in the real contest even the prompt will not show, due to the internet restriction).
Indeed, code highlighting, and other IDE features are working because of the C/C++
extension.
Came to the same conclusion in the meantime. Thanks for confirming.
Also, when I dismiss the prompt, I can ask for it not to be shown again and this seems to work. So, if it's easy to switch it off pre-emptively, would be nice, but we can instruct our contestants to do it manually as well. (I'm not a daily VSCode user myself, so not fluent in its settings.)
This (the 4th option, or the 4.5th option outlined in the comment) may be an option, if it can be applied user-wide, not only workspace-wide?
extensions.ignoreRecommendations: true
,extensions.unwantedRecommendations: ["..."]
If someone (either from HTC, or anyone interested) is eager to investigate if there is a user-wide configuration option which resolves this issue (I cannot even really reproduce the prompt without restoring from snapshot), I would be happy to add it.
This looks like a minor, one-time annoyance. (note that there is an option to stop recommending extensions)
In the end, this is indeed a quite trivial annoyance. Feel free to close the issue if there's no easy fix. You probably have more important issues to work on :)
When I start VSCode and open a C++ source file, I get a prompt asking me to install the C/C++ Extension Pack, which should already be installed, according to https://ioi2023.hu/contest-environment/.
With network disconnected, the installation will actually fail, so this does not seem to be the case of some local initialization on first start of an already installed component.
Curiously enough, after dismissing the error message, syntax highlighting and code completion, compilation, and debugging all seem to work, so it's more of an annoyance than an actual bug. But perhaps still can be corrected?