From 0da958a2d53ce1f614041dfd0308d746bf42b546 Mon Sep 17 00:00:00 2001 From: eta Date: Wed, 16 Sep 2020 13:10:41 +0100 Subject: [PATCH] don't splurt error backtraces at the user - Getting hit with a massive backtrace is slightly overwhelming. It also is a potential privacy issue, seeing as phone numbers (etc.) might be printed as part of the call stack... --- stuff.lisp | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/stuff.lisp b/stuff.lisp index 21c2114..1b7ad0b 100644 --- a/stuff.lisp +++ b/stuff.lisp @@ -260,11 +260,9 @@ WhatsXMPP represents users as u440123456789 and groups as g1234-5678." (defun wa-handle-error (comp conn jid err bt) (with-wa-handler-context (comp conn jid) - (format *debug-io* "~&whatscl error for ~A: ~A~%" jid err) + (format *debug-io* "~&whatscl error for ~A: ~A~%Backtrace:~A~%" jid err bt) (admin-msg comp jid (format nil "A programming error has been detected and your connection has been aborted unexpectedly.~%Report the following error to the bridge admin: ~A" err)) - (admin-msg comp jid - (format nil "Backtrace:~%~A" bt)) (admin-msg comp jid "(Disabling automatic reconnections.)") (admin-presence comp jid "Programming error" "xa") (remhash jid (component-whatsapps comp))))