Skip to content

Commit 262963c

Browse files
committed
fix: resolve conflict in extensionHostProcessSetup.ts
From what I can tell, they added these `performance.mark` calls. Not sure exactly what they do, but my guess is they're supposed to help with measuring extension performance?
1 parent 7bf1fd9 commit 262963c

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

lib/vscode/src/vs/workbench/services/extensions/node/extensionHostProcessSetup.ts

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -313,12 +313,9 @@ function connectToRenderer(protocol: IMessagePassingProtocol): Promise<IRenderer
313313
}
314314

315315
export async function startExtensionHostProcess(): Promise<void> {
316-
<<<<<<< HEAD
317316
proxyAgent.monkeyPatch(true);
318317

319-
=======
320318
performance.mark(`code/extHost/willConnectToRenderer`);
321-
>>>>>>> 89b6e0164fa770333755b11504e19a4232b1a2d4
322319
const protocol = await createExtHostProtocol();
323320
performance.mark(`code/extHost/didConnectToRenderer`);
324321
const renderer = await connectToRenderer(protocol);

0 commit comments

Comments
 (0)