From 49c7e692f22c8c1f61fa0ea1f8ccb9be09584269 Mon Sep 17 00:00:00 2001
From: Nico Flaig <nflaig@protonmail.com>
Date: Wed, 5 Jul 2023 09:44:49 +0200
Subject: [PATCH] chore: remove explicit exit after beacon node closed

---
 packages/cli/src/cmds/beacon/handler.ts | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/packages/cli/src/cmds/beacon/handler.ts b/packages/cli/src/cmds/beacon/handler.ts
index 4c71e4714dd2..af34cf861697 100644
--- a/packages/cli/src/cmds/beacon/handler.ts
+++ b/packages/cli/src/cmds/beacon/handler.ts
@@ -130,9 +130,6 @@ export async function beaconHandler(args: BeaconArgs & GlobalArgs): Promise<void
         try {
           await node.close();
           logger.debug("Beacon node closed");
-          // Explicitly exit until active handles issue is resolved
-          // See https://github.com/ChainSafe/lodestar/issues/5642
-          process.exit(0);
         } catch (e) {
           logger.error("Error closing beacon node", {}, e as Error);
           // Make sure db is always closed gracefully