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 473851FF136 for ; Mon, 04 May 2026 14:43:35 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 84A8C20A63; Mon, 4 May 2026 14:43:34 +0200 (CEST) From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?= To: pbs-devel@lists.proxmox.com, Robert Obkircher Subject: applied-series: [PATCH v1 proxmox-backup 0/2] improve logging Date: Mon, 4 May 2026 14:43:18 +0200 Message-ID: <177789858070.582169.6956723670377827681.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260430092022.31857-1-r.obkircher@proxmox.com> References: <20260430092022.31857-1-r.obkircher@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: 1777898504420 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.054 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: SHZSNLVBMTUUBXQ7G5ICUJ3ZJSDMBDOW X-Message-ID-Hash: SHZSNLVBMTUUBXQ7G5ICUJ3ZJSDMBDOW X-MailFrom: f.gruenbichler@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 Thu, 30 Apr 2026 11:17:42 +0200, Robert Obkircher wrote: > The first patch adds more context to a log message and the second one > replaces all uses of `:#?` with `:#`. > > Robert Obkircher (2): > datastore: improve error if prune can't lock a snapshot for deletion > tree-wide: avoid struct-style debug representation of anyhow errors > > [...] Applied, thanks! [1/2] datastore: improve error if prune can't lock a snapshot for deletion commit: ebf5d21312d1a23308a68b5bcb4982b61b295e1c [2/2] tree-wide: avoid struct-style debug representation of anyhow errors commit: f0bfc16fdf1fdcb486fa35d0b20df2c27a2c4636 Best regards, -- Fabian Grünbichler