fix(signaling): log the sanitized reason when signaling fails to connect

The WebSocket transport already reduces errors to a category or HTTP status
without the token or endpoint, so log it instead of 'details omitted' to tell
a refused upgrade from a network failure (#166).

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
VallierDevandClaude Opus 5.5 committed 2026-11-03 15:34:34 +08:00
1 parent c0abdeae72
commit 81e9ccfa05
2 files changed
+3 -3

No files matched your search

+2 -2
View File
@@ -855,8 +855,8 @@ async fn serve(mut capture: Arc<ScreenCapture>, input: Arc<InputInjector>, shutd
Arc::new(cli)
}
Err(e) => {
let _ = e;
log::error!("Failed to connect signaling; retrying in 5s (details omitted)");
// ws_transport errors carry only a category or HTTP status, never the token or URL.
log::error!("Failed to connect signaling; retrying in 5s: {e}");
tokio::time::sleep(tokio::time::Duration::from_secs(5)).await;
continue;
}
+1 -1
View File
@@ -248,7 +248,7 @@ impl SignalingClient {
let mut req = ws_url
.clone()
.into_client_request()
.map_err(|e| format!("Invalid WS request: {}", e))?;
.map_err(|_| "Invalid WS request".to_string())?;
req.headers_mut().insert(
"X-NRD-AUTH",