From 2d1698a120ca5266f4c619acb609908a6b2faf65 Mon Sep 17 00:00:00 2001
From: Deirdre Connolly <deirdre@zfnd.org>
Date: Sat, 12 Dec 2020 11:31:46 -0500
Subject: [PATCH] Comment out Sentry stacktraces for now

While panic = abort, Sentry collects the same one-line stack trace for all panics,
making it incorrectly dedupe different errors into one.
---
 zebrad/src/sentry.rs | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/zebrad/src/sentry.rs b/zebrad/src/sentry.rs
index ebea0d586..bf64fdb90 100644
--- a/zebrad/src/sentry.rs
+++ b/zebrad/src/sentry.rs
@@ -1,3 +1,4 @@
+#[allow(unused_imports)]
 use sentry::{
     integrations::backtrace::current_stacktrace,
     protocol::{Event, Exception, Mechanism},
@@ -15,7 +16,11 @@ where
             ..Default::default()
         }),
         value: Some(msg.to_string()),
-        stacktrace: current_stacktrace(),
+        // Sentry does not handle panic = abort well yet, and when gibven this
+        // stacktrace, it consists only of this line, making Sentry dedupe
+        // events together by their stacetrace fingerprint incorrectly.
+        //
+        // stacktrace: current_stacktrace(),
         ..Default::default()
     };