Garrett Campbell

@blubberdiblub @danniesim Sorry for the delay on reviewing this. I've taken a note to discuss this PR with the team next week. In the meantime, @danniesim it would be helpful...

Hi, @danniesim. Unfortunately, we plan to close this PR and not merge it into the codebase. This is because we don't want to add a top-level setting into the extension...

@gerard-ryan-immersaview Does this issue still reproduce if you clear the setting `cmake.generator`? Thanks, adding this issue to the backlog so we can track better and investigate when we can.

@sinemakinci1 FYI.

Closed, fixed in #3746

@nikoprotic Thanks for posting the issue. I also occasionally see this, though it has always been very flaky for me. Do you find that this is a flaky issue? Or...

@nikoprotic No worries. We'll investigate this as soon as we have capacity.

@v-ericawu I think I know what the issue is. If you close the CMakePresets.json file, reload VS Code, and then do something to ensure that the extension activates (i.e. run...

Currently investigating whether we should add `onFileSystem:cmake-tools-schema` activation event, or wait for this bug: https://github.com/microsoft/vscode/issues/211116, to be solved (or at least answered).

@KnoerleMaTLS @Evelyn-001 Does configuring from CMake Tools and the fact that it doesn't prompt for a github password block the completion of your configure? Or is it just that you're...