From 180d30dc5f751bb2016b26954c188543f3b95ab9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Micha=C5=82=20Muska=C5=82a?= <micmus@meta.com>
Date: Tue, 23 Jul 2024 01:48:53 -0700
Subject: [PATCH] erlang service: remove spurious trap_exit call

Summary:
I don't really understand why it's there - this is called in the supervisor, that should be trapping exits already. The process itself didn't do any trapping and was not prepared to handle `EXIT` messages. This seems to be some bad migration.

Created from CodeHub with https://fburl.com/edit-in-codehub

Reviewed By: alanz

Differential Revision: D60050802

fbshipit-source-id: 3b46b089e966569f6f17d7799d31cbfa5f6571ef
---
 erlang_service/src/erlang_service_server.erl | 1 -
 1 file changed, 1 deletion(-)

diff --git a/erlang_service/src/erlang_service_server.erl b/erlang_service/src/erlang_service_server.erl
index 73b281fc9..dbe90e49d 100644
--- a/erlang_service/src/erlang_service_server.erl
+++ b/erlang_service/src/erlang_service_server.erl
@@ -56,7 +56,6 @@
 %%==============================================================================
 -spec start_link() -> {ok, pid()}.
 start_link() ->
-    process_flag(trap_exit, true),
     {ok, _Pid} = gen_server:start_link({local, ?SERVER}, ?MODULE, noargs, []).
 
 -spec process(binary()) -> ok.