TraceServer: Remove extra server-exit stopOrReset

Before this fix, an extra stopOrReset was performed for nothing, upon
stopping (thus exiting) the previously started server. This caused an
extra (confusing) warning message being showed which was unrelated
anyway. The latter was about not stopping, but this use case is truly
about restarting the server.

Contributes to fixing #8.

Signed-off-by: Marco Miller <marco.miller@ericsson.com>

Author: marco-miller

src/trace-server.ts

@@ -7,7 +7,6 @@ import * as vscode from 'vscode';
 // -for naming consistency purposes across sibling extensions/settings:
 const section = 'trace-server.traceserver';
 
-const exit = 'exit';
 const key = 'pid';
 const millis = 10000;
 const none = -1;
@@ -41,7 +40,7 @@ export class TraceServer {
             let id: NodeJS.Timeout;
             // recovering from workspaceState => no this.server set
             if (this.server) {
-                this.server.once(exit, () => {
+                this.server.once('exit', () => {
                     this.showStatus(false);
                     clearTimeout(id);
                 });
@@ -144,9 +143,6 @@ export class TraceServer {
                 while (true) {
                     if (await this.isUp()) {
                         this.showStatus(true);
-                        this.server?.once(exit, () => {
-                            this.stopOrReset(context);
-                        });
                         clearTimeout(timeoutId);
                         break;
                     }