From 9e352ae8432db2644bd7b432c5682576e5318a71 Mon Sep 17 00:00:00 2001
From: Nico Flaig <nflaig@protonmail.com>
Date: Wed, 12 Jul 2023 09:29:46 +0200
Subject: [PATCH] Re-add explicit exit after beacon node closed

This reverts commit 1de881b7776284c6dd56f146ac55ef3df040f98d.
---
 packages/cli/src/cmds/beacon/handler.ts | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/packages/cli/src/cmds/beacon/handler.ts b/packages/cli/src/cmds/beacon/handler.ts
index af34cf861697..4c71e4714dd2 100644
--- a/packages/cli/src/cmds/beacon/handler.ts
+++ b/packages/cli/src/cmds/beacon/handler.ts
@@ -130,6 +130,9 @@ 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