From d9fb9e53c8a3648fee63e0bfe98918d237352a98 Mon Sep 17 00:00:00 2001 From: Thomas Eizinger Date: Mon, 18 Nov 2024 18:15:04 +0000 Subject: [PATCH] chore(snownet): print error code for unhandled message (#7367) All our logic for handling errors is based on the error code. Even though there should be a 1:1 mapping between error code and reason phrase, I am seeing odd reports in Sentry for a case that we should be handling but aren't. --- rust/connlib/snownet/src/allocation.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rust/connlib/snownet/src/allocation.rs b/rust/connlib/snownet/src/allocation.rs index fea494210..58e2a593b 100644 --- a/rust/connlib/snownet/src/allocation.rs +++ b/rust/connlib/snownet/src/allocation.rs @@ -443,7 +443,7 @@ impl Allocation { _ => {} } - tracing::warn!(error = %error.reason_phrase(), "TURN request failed"); + tracing::warn!(error = %error.reason_phrase(), code = %error.code(), "TURN request failed"); return true; }