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 4D6D81FF183 for ; Wed, 10 Sep 2025 17:13:42 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 069352610B; Wed, 10 Sep 2025 17:13:46 +0200 (CEST) From: Thomas Lamprecht To: pdm-devel@lists.proxmox.com, Dominik Csapak Date: Wed, 10 Sep 2025 17:12:05 +0200 Message-ID: <175751711174.2710202.5426448965133692144.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20250909082608.1018103-1-d.csapak@proxmox.com> References: <20250909082608.1018103-1-d.csapak@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1757517191333 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.030 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: [pdm-devel] applied: [RFC PATCH datacenter-manager] server: api: resources: use root cause for errors for remote fetching X-BeenThere: pdm-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Datacenter Manager development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Datacenter Manager development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pdm-devel-bounces@lists.proxmox.com Sender: "pdm-devel" On Tue, 09 Sep 2025 10:25:51 +0200, Dominik Csapak wrote: > when we can't reach a remote for any reason, we want to return the error > as a string here over the API. Since most errors that can occur here are > client/network related (wrong credentials, no route to host, timeout, > etc.) converting this error directly to a string gives us > errors like: > > `client error (Connect)` > > [...] Applied, thanks! Added logging the full context as tracing::debug message like Wolfgang suggested in a follow up. [1/1] server: api: resources: use root cause for errors for remote fetching commit: 56a80782168ce5cc7f5da6eaafe533d9f791ef38 _______________________________________________ pdm-devel mailing list pdm-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel