don't run debug server as separate process

This way, we can debug the debug server the same way we debug the
rest of the extension

Author: dlech

src/debugServer.ts

@@ -13,8 +13,7 @@ export interface LaunchRequestArguments extends DebugProtocol.LaunchRequestArgum
     interactiveTerminal: boolean;
 }
 
-
-class Ev3devBrowserDebugSession extends DebugSession {
+export class Ev3devBrowserDebugSession extends DebugSession {
     protected initializeRequest(response: DebugProtocol.InitializeResponse,
         args: DebugProtocol.InitializeRequestArguments): void {
         if (response.body) {
@@ -44,4 +43,6 @@ class Ev3devBrowserDebugSession extends DebugSession {
     }
 }
 
-DebugSession.run(Ev3devBrowserDebugSession);
+if (require.main === module) {
+    DebugSession.run(Ev3devBrowserDebugSession);
+}

src/extension.ts

@@ -1,12 +1,13 @@
 import * as fs from 'fs';
+import * as net from 'net';
 import * as os from 'os';
 import * as path from 'path';
 import * as ssh2Streams from 'ssh2-streams';
 import * as temp from 'temp';
 
 import * as vscode from 'vscode';
 
-import { LaunchRequestArguments } from './debugServer';
+import { Ev3devBrowserDebugSession, LaunchRequestArguments } from './debugServer';
 import { Brickd } from './brickd';
 import { Device } from './device';
 import {
@@ -34,6 +35,7 @@ export function activate(context: vscode.ExtensionContext): void {
     resourceDir = context.asAbsolutePath('resources');
 
     ev3devBrowserProvider = new Ev3devBrowserProvider();
+    const factory = new Ev3devDebugAdapterDescriptorFactory();
     context.subscriptions.push(
         output, ev3devBrowserProvider,
         vscode.window.registerTreeDataProvider('ev3devBrowser', ev3devBrowserProvider),
@@ -52,10 +54,33 @@ export function activate(context: vscode.ExtensionContext): void {
         vscode.commands.registerCommand('ev3devBrowser.action.pickDevice', () => pickDevice()),
         vscode.commands.registerCommand('ev3devBrowser.action.download', () => downloadAll()),
         vscode.commands.registerCommand('ev3devBrowser.action.refresh', () => refresh()),
-        vscode.debug.onDidReceiveDebugSessionCustomEvent(e => handleCustomDebugEvent(e))
+        vscode.debug.onDidReceiveDebugSessionCustomEvent(e => handleCustomDebugEvent(e)),
+        vscode.debug.registerDebugAdapterDescriptorFactory('ev3devBrowser', factory),
     );
 }
 
+class Ev3devDebugAdapterDescriptorFactory implements vscode.DebugAdapterDescriptorFactory {
+    private server?: net.Server;
+
+    createDebugAdapterDescriptor(session: vscode.DebugSession, executable: vscode.DebugAdapterExecutable | undefined): vscode.ProviderResult<vscode.DebugAdapterDescriptor> {
+        if (!this.server) {
+            // start listening on a random port
+            this.server = net.createServer(socket => {
+                const session = new Ev3devBrowserDebugSession();
+                session.setRunAsServer(true);
+                session.start(<NodeJS.ReadableStream>socket, socket);
+            }).listen(0);
+        }
+
+        // make VS Code connect to debug server
+        return new vscode.DebugAdapterServer(this.server.address().port);
+    }
+
+    dispose() {
+        this.server?.close();
+    }
+}
+
 // this method is called when your extension is deactivated
 export function deactivate(): void {
     // The "temp" module should clean up automatically, but do this just in case.