Fix bug where stop()+start() in admin client could trigger reconnects

This didn't actually break normal behaviour, but resulted in a bunch of
failing background reconnections for 10s or so, which did block process
exit if it happened at the end of a test suite, for example.

Author: pimterry

src/client/admin-client.ts

@@ -269,11 +269,12 @@ export class AdminClient<Plugins extends { [key: string]: AdminPlugin<any, any>
             // If never connected successfully, we do nothing.
         });
 
-        targetStream.on('finish', () => { // Client has shutdown
+        targetStream.on('end', () => { // Client has shutdown
             // Ignore any further WebSocket events - the websocket stream is no longer useful
             wsStream.removeAllListeners('connect');
             wsStream.removeAllListeners('ws-close');
             wsStream.destroy();
+            streamConnected = false;
         });
 
         return wsStream;
@@ -291,6 +292,9 @@ export class AdminClient<Plugins extends { [key: string]: AdminPlugin<any, any>
     ) {
         this.emit('stream-reconnecting');
 
+        // If the client stops running, stop retrying:
+        if (!(await this.running)) return;
+
         // Unclean shutdown means something has gone wrong somewhere. Try to reconnect.
         const newStream = this.attachStreamWebsocket(adminSessionBaseUrl, targetStream);