From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 418A21FF15C for ; Fri, 14 Nov 2025 00:41:18 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id EE6A72076; Fri, 14 Nov 2025 00:42:10 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Daniel Kral Date: Fri, 14 Nov 2025 00:41:49 +0100 Message-ID: <176307723389.3062351.14222721460770345434.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20250415071123.36921-1-d.kral@proxmox.com> References: <20250415071123.36921-1-d.kral@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1763077300898 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.023 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] applied: [RFC storage v2 1/3] api: smart: return unknown health instead of error message X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" On Tue, 15 Apr 2025 09:11:21 +0200, Daniel Kral wrote: > In case of an error, the WebGUI expects the SMART data API endpoint to > return a health value, but it will return an error message directly. To > make this more user friendly, mask the error in the API handler. > > Applied (better late than never..) with merge conflict from perltidy reformatting resolved, thanks! [1/3] api: smart: return unknown health instead of error message commit: 0d2df3048acb5c414ad8abeccb65c86d899166b3 [2/3] disks: get: separate error path for retrieving SMART data commit: b6c18e91165e50dd1470c973b660a9a703c2cdd6 [3/3] fix #6224: disks: get: set timeout for retrieval of SMART stat data commit: ebec84ff8765def023b74aeba722fc09d9a9f87d _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel