From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 11C861FF2A8 for ; Tue, 2 Jul 2024 14:19:36 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 36BE51D631; Tue, 2 Jul 2024 14:19:50 +0200 (CEST) Date: Tue, 2 Jul 2024 14:19:46 +0200 (CEST) From: =?UTF-8?Q?Fabian_Gr=C3=BCnbichler?= To: Proxmox VE development discussion Message-ID: <112887466.2740.1719922786767@webmail.proxmox.com> In-Reply-To: References: MIME-Version: 1.0 X-Priority: 3 Importance: Normal X-Mailer: Open-Xchange Mailer v7.10.6-Rev65 X-Originating-Client: open-xchange-appsuite X-SPAM-LEVEL: Spam detection results: 0 AWL 0.051 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com] Subject: Re: [pve-devel] Feature Request: Enhancing Error Messaging 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 Cc: Rovshan Pashayev Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" > Rovshan Pashayev via pve-devel hat am 02.07.2024 12:50 CEST geschrieben: > We kindly request the implementation of enhanced error messaging. Currently, all errors and failures are combined into a single string, making it difficult to identify and address specific issues. which errors? for which actions/API endpoints/..? > Please consider introducing error codes or a similar mechanism to provide a structured format for error reporting. This would improve the user experience and expedite troubleshooting during third-party backup processes. we try to keep the errors meaningful and easy to understand. if you have concrete examples that could benefit from more detail or changed contents, feel free to file issues at https://bugzilla.proxmox.com we are not planning to add error codes (like E1234) to our error messages at the moment - in our experience, those don't provide much added benefit at the level of interaction PVE usually provides. structured error types can make sense for low level interfaces (where callers might decide on a course of action based on the error, like retrying). note that we do differentiate between lacking permissions, bad parameters and other errors also on the API level. _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel