Microsoft/vscode
1
0
Fork 0
mirror of https://github.com/microsoft/vscode.git synced 2026-05-08 17:19:48 +01:00
Code Issues Packages Projects Releases Wiki Activity

Use host+port instead of string for managed tunnel (#192762)

Browse Source 
Fixes https://github.com/microsoft/vscode-remote-release/issues/8933
This commit is contained in:
Alex Ross
2023-09-11 13:18:29 +02:00
committed by GitHub
parent b5b5cade57
commit 59babb4ccc
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/vs/workbench/api/node/extHostTunnelService.ts
+2 -2
View File
@@ -22,7 +22,7 @@ import { NodeRemoteTunnel } from 'vs/platform/tunnel/node/tunnelService';
import { IExtHostInitDataService } from 'vs/workbench/api/common/extHostInitDataService';
import { IExtHostRpcService } from 'vs/workbench/api/common/extHostRpcService';
import { ExtHostTunnelService } from 'vs/workbench/api/common/extHostTunnelService';
import { CandidatePort } from 'vs/workbench/services/remote/common/tunnelModel';
import { CandidatePort, parseAddress } from 'vs/workbench/services/remote/common/tunnelModel';
import * as vscode from 'vscode';
export function getSockets(stdout: string): Record<string, { pid: number; socket: number }> {
@@ -349,7 +349,7 @@ export class NodeExtHostTunnelService extends ExtHostTunnelService {
const disposeEmitter = new Emitter<void>();
return {
localAddress: t.localAddress,
localAddress: parseAddress(t.localAddress) ?? t.localAddress,
remoteAddress: { port: t.tunnelRemotePort, host: t.tunnelRemoteHost },
onDidDispose: disposeEmitter.event,
dispose: () => {