fix(API): surface wallet connection errors in trusted peer view

TheLastCicada · TheLastCicada · commit e4e12df103af · 2026-05-13T13:52:46.000-07:00
getWalletConnections catches errors internally and returns
{ success: false, error } instead of throwing, so settle() always
sees ok: true. Check value.success before treating connections as
valid, and surface the inner error when the wallet call failed.
diff --git a/src/routes/diagnostics.js b/src/routes/diagnostics.js
@@ -191,7 +191,7 @@ const buildTrustedPeerView = (connectionsResult, chiaConfigResult) => {
     view.chiaConfigError = chiaConfigResult.error;
   }
 
-  if (connectionsResult?.ok) {
+  if (connectionsResult?.ok && connectionsResult.value?.success !== false) {
     const connections = connectionsResult.value?.connections || [];
     view.connected = connections.map((c) => {
       const trusted = !!(
@@ -201,7 +201,9 @@ const buildTrustedPeerView = (connectionsResult, chiaConfigResult) => {
       return { peerHost: c.peerHost, peerPort: c.peerPort, type: c.type, trusted };
     });
   } else if (connectionsResult) {
-    view.connectionsError = connectionsResult.error;
+    view.connectionsError = connectionsResult.ok
+      ? connectionsResult.value?.error || 'wallet connections unavailable'
+      : connectionsResult.error;
   }
 
   return view;
