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 15D2F1FF183 for ; Tue, 28 Apr 2026 03:27:13 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A6E09BD1; Tue, 28 Apr 2026 03:27:12 +0200 (CEST) From: Thomas Lamprecht To: pbs-devel@lists.proxmox.com, Christian Ebner Subject: applied: [PATCH proxmox-backup] client: show full error context in single line on upload errors Date: Tue, 28 Apr 2026 03:26:55 +0200 Message-ID: <177733961473.2651958.6614933903946250384.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260427125955.653377-1-c.ebner@proxmox.com> References: <20260427125955.653377-1-c.ebner@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1777339534244 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.003 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 Message-ID-Hash: SG6IHGBMXT6SOR3RRCDOVBJNQYYLYPJW X-Message-ID-Hash: SG6IHGBMXT6SOR3RRCDOVBJNQYYLYPJW X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Mon, 27 Apr 2026 14:59:55 +0200, Christian Ebner wrote: > Since commit 07cb3e7f7 ("client: pxar: optionally split metadata and > payload streams") there are possibly multiple upload streams (data > and metadata archive), errors for each propagated accordingly. > Since this reformatted the error without explicitly including the > context, the resulting error messages are lacking crucial information. > > Reformat the error with full context. > > [...] Applied, thanks! [1/1] client: show full error context in single line on upload errors commit: 456a43380c16f7865604d30fa9bf23a131dd5c1e