From 8e830dfec18e04b1c37ce841245a835cc7aaada2 Mon Sep 17 00:00:00 2001 From: Tim Bradgate Date: Sun, 24 May 2026 11:02:01 +0100 Subject: [PATCH] Fix V3 config backups tab: NOOP WebSocket warning and BTable sort crash - Add `case 'NOOP': break;` to the WebSocket handleMessage switch so the intentional NOOP carrier OP (used to deliver ACTION-based messages on connect) is silently consumed instead of falling to the default warn log. - Remove invalid BVN 0.45.x props `sort-by="created_at"` and `:sort-desc="true"` from ConfigBackups BTable. BVN replaced the old BV2 string/bool pair with `v-model:sort-by` (BTableSortBy[]); passing a string caused computedItems to call `"created_at"?.filter(fn)` which threw TypeError. Backend already returns backups sorted newest-first. Co-Authored-By: Claude Sonnet 4.6 --- client-v3/src/components/config/ConfigBackups.vue | 2 +- client-v3/src/composables/useWebSocket.ts | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/client-v3/src/components/config/ConfigBackups.vue b/client-v3/src/components/config/ConfigBackups.vue index f220184f..e5ba6042 100644 --- a/client-v3/src/components/config/ConfigBackups.vue +++ b/client-v3/src/components/config/ConfigBackups.vue @@ -5,7 +5,7 @@ {{ count }} {{ count === 1 ? 'backup' : 'backups' }} · {{ formatBytes(totalSizeBytes) }} total

- + diff --git a/client-v3/src/composables/useWebSocket.ts b/client-v3/src/composables/useWebSocket.ts index 5c367299..24489d92 100644 --- a/client-v3/src/composables/useWebSocket.ts +++ b/client-v3/src/composables/useWebSocket.ts @@ -91,6 +91,8 @@ async function handleMessage(msg: WsMessage): Promise { case 'RELOAD_CLIENT': window.location.reload(); break; + case 'NOOP': + break; default: log.warn(`Unknown OP received from WebSocket: ${msg.OP}`); }