Extension not activating if remote has ssh config includes

[gnammix]

Environment

• OS and Version: Windows 11
• VS Code Version: 1.104.1
• C/C++ Extension Version: 1.27.7
• If using SSH remote, specify OS of remote machine: Ubuntu 24.04 LTS

Bug Summary and Steps to Reproduce

Bug Summary:
This is quite odd but I'm able to reproduce it 100%.
I'm not sure why this happens or if this issue is in vscode-cpptools or vscode-remote-ssh.
But changing the Include line as written below fixes it, so maybe it is worth checking/easy to fix.

Extension doesn't load.
No actions seems to work (formatting, go to definitions, header/cpp switch, ...).
Trying to format the whole document pops up request to install a cpp formatter.

The extension show "Activating extension..." on the status but nothing else happens.
Even "C/C++: Log Diagnostics" doesn't do anything.

Steps to reproduce:
Add

Include **/config

to remote ssh config.

Removing or changing it to (for example):

Include config.d/*

fix the issue, the extension activate and work correctly.

Expected behavior:
Extension activate correctly.

Configuration and Logs

I cannot generate any log "C/C++: Log Diagnostics" doesn't do anything.

Other Extensions

The whole vscode-remote suite is installed.
cmake-tools

Additional context

No response

[gnammix]

I also checked if this was a regression.
v1.12.4 seems to be the last one not affected.

[Colengms]

Hi @gnammix . I'm not able to repro by adding just Include **/config to an SSH config file (without having something locally that would actually be included by it) and remoting into an Ubuntu system.

I'm not sure how that syntax simply existing in your config file would impact the C/C++ Extension. I assume the issue would have to be related to something being pulled in from (local) files it causes to be included. Can you identify what contents within the files you are including are necessary to repro the issue, and let us know if that still seems to point to an issue with the C/C++ extension itself?

[gnammix]

Hi @Colengms , just to be sure (and I know it sounds weird) the Include in my case is on the remote system.

The tree looks like that:

/home/gnammix/.ssh
 ├──bitbucket
 │  ├──config
 │  ├──identity
 │  └──identity.pub
 ├──config
 ├──github
 │  ├──config
 │  ├──identity
 │  └──identity.pub
 known_hosts 
 known_hosts.old

content is nothing special:

/home/gnammix/.ssh/config:

Include **/config

Host *
  ForwardAgent no
  AddKeysToAgent no
  Compression no
  ServerAliveInterval 0
  ServerAliveCountMax 3
  HashKnownHosts no
  UserKnownHostsFile ~/.ssh/known_hosts
  ControlMaster no
  ControlPath ~/.ssh/master-%r@%n:%p
  ControlPersist no

/home/gnammix/.ssh/github/config:

Host github.com
  User gnammix
  IdentityFile ~/.ssh/github/identity

/home/gnammix/.ssh/bitbucket/config:

Host somehostname
  HostName somehostname
  User user
  IdentityFile ~/.ssh/bitbucket/identity

[gnammix]

Regarding the version that seems to be affected:

From 1.13.6 I have the issue
1.12.4 doesn't have

I diffed the two releases but really cannot see anything obviously bad.

[sean-mcmanus]

@gnammix Does Help->Toggle Developer Tools->Console show an errors related to the issue? Do you have a notification prompt hidden in the bottom right corner that needs responding to? You could also potentially debug the TypeScript of our extension -- it might be stuck on some await call.

[gnammix]

I'm not very fluent in js, log do not seems to contain any obvious error, so cannot help with that but I've attached:

• vagrant machine configuration (running on Windows 11/Hyper-v) I used to repro
• minimal cmake project I used to test if cpp extension was functional
• dump of minimal /.ssh folder triggering the error
• console log for a run where it is working and one where it is not

If you need anything more specific feel free to ask.

console_logs.zip
minimal_cmake_example.zip
ssh.zip
Vagrantfile.zip