From 02a0d974f36eabaf79d8a5e2e534bf0850e7e6da Mon Sep 17 00:00:00 2001
From: David Lechner <david@pybricks.com>
Date: Wed, 19 Apr 2023 11:59:51 -0500
Subject: [PATCH] hub/sagas: don't stop user program after connect

Since we now have periodic status messages, we don't need to do anything
to get into a known state.

This caused unexpected behavior when connecting to a hub that is already
connected in a second window.
---
 src/hub/sagas.ts | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/src/hub/sagas.ts b/src/hub/sagas.ts
index 6fefe22a..09ceb8d7 100644
--- a/src/hub/sagas.ts
+++ b/src/hub/sagas.ts
@@ -14,7 +14,6 @@ import {
     takeEvery,
 } from 'typed-redux-saga/macro';
 import { alertsShowAlert } from '../alerts/actions';
-import { bleDidConnectPybricks } from '../ble/actions';
 import { didFailToWrite, didWrite, write } from '../ble-nordic-uart-service/actions';
 import { nordicUartSafeTxCharLength } from '../ble-nordic-uart-service/protocol';
 import {
@@ -429,6 +428,4 @@ export default function* (): Generator {
     yield* takeEvery(downloadAndRun, handleDownloadAndRun);
     yield* takeEvery(hubStartRepl, handleHubStartRepl);
     yield* takeEvery(hubStopUserProgram, handleStopUserProgram);
-    // calling stop right after connecting should get the hub into a known state
-    yield* takeEvery(bleDidConnectPybricks, handleStopUserProgram);
 }