Unable to start remote Agents app session from Windows to Linux

[rzhao271]

Testing #311105

1. Create a dev tunnel from a code-insiders install within WSL by running code-insiders tunnel. I also tried running an agent host in that WSL instance at the same time.
2. From Windows, open the Agents app and try connecting to the dev tunnel session.
3. 🐛 No dev tunnels with agent host support were found.

Image below shows the WSL tunnel working fine with insiders.vscode.dev on Windows.

[connor4312]

Please install the devtunnel CLI https://learn.microsoft.com/en-us/azure/developer/dev-tunnels/get-started?tabs=macos and run devtunnel list so we can see what the tunnel looks like.

[rzhao271]

I'm guessing that devtunnel isn't the same as code-insiders tunnel. Here's some output of list after I started both a devtunnel and a code-insiders tunnel in WSL. The Agents app on my Windows machine is still unable to connect to either of them.

Found 1 tunnel.

Tunnel ID                           Host Connections     Labels                    Ports                Expiration                Description
tidy-plane-v89045t.usw2             1                                              0                    30 days

[connor4312]

That tunnel is lacking any Labels, so we do not know it's a github/agent-host compatible dev tunnel. Not sure how that could happen...

[rzhao271]

The tunnel listed above is the devtunnel one. devtunnel doesn't seem to detect tunnels created by VS Code. I followed the instructions on Learn to create and host the devtunnel tunnel. When logging in, I was forced to select a Microsoft account.

[connor4312]

You can log in using devtunnel login --github to github. It'll only show tunnels for your currently authed account.

[rzhao271]

Found 2 tunnels.

Tunnel ID                           Host Connections     Labels                    Ports                Expiration                Description
neat-plane-p9ttflh.usw2             1                    a20,protocolv5,vscod...   2                    30 days
sneaky-chair-2n46g6h.usw2           0                    laptop-u01f9qsg,prot...   2                    29 days

That seemed off to me so I deleted them and recreated another one with code-insiders tunnel

Found 1 tunnel.

Tunnel ID                           Host Connections     Labels                    Ports                Expiration                Description
kind-book-gx2mb1p.usw2              0                    a20,protocolv5,vscod...   2                    30 days

I'm still unable to connect from Windows.

[connor4312]

I'm quite unsure what is going on here. If you're able to, it'd be helpful to open OSS and set breakpoints around the listTunnels here

vscode/src/vs/platform/agentHost/node/tunnelAgentHostService.ts

Lines 99 to 127 in 6ee3ae6

	const tunnels = await client.listTunnels(undefined, undefined, {
	labels: [TUNNEL_LAUNCHER_LABEL],
	requireAllLabels: true,
	includePorts: true,
	tokenScopes: ['connect'],
	});
	for (const tunnel of tunnels) {
	const info = this._parseTunnelInfo(tunnel);
	if (info && info.protocolVersion >= TUNNEL_MIN_PROTOCOL_VERSION) {
	results.push(info);
	seen.add(info.tunnelId);
	}
	}
	} catch (err) {
	this._logService.error(`${LOG_PREFIX} Failed to enumerate tunnels`, err);
	}
	// Look up additional tunnels by name
	if (additionalTunnelNames) {
	for (const tunnelName of additionalTunnelNames) {
	try {
	const [tunnel] = await client.listTunnels(undefined, undefined, {
	labels: [tunnelName, TUNNEL_LAUNCHER_LABEL],
	requireAllLabels: true,
	includePorts: true,
	tokenScopes: ['connect'],
	limit: 1,
	});

I think either the tunnels are not being returned or we error perhaps parsing their details. Capturing the tunnel object, if any, would be helpful (make sure to remove any access token when posting to the issue)