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 1EF411FF13C for ; Thu, 05 Feb 2026 19:10:59 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 2FDAD183E6; Thu, 5 Feb 2026 19:11:31 +0100 (CET) From: Thomas Lamprecht To: pdm-devel@lists.proxmox.com, Lukas Wagner Subject: applied: [PATCH datacenter-manager 2/5] parallel fetcher: make sure to inherit log context Date: Thu, 5 Feb 2026 19:08:21 +0100 Message-ID: <177031489314.1855911.2132922520727709653.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260204152723.482258-3-l.wagner@proxmox.com> References: <20260204152723.482258-1-l.wagner@proxmox.com> <20260204152723.482258-3-l.wagner@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: 1770315009033 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.022 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 Message-ID-Hash: SKR3IRAPPOD5AWSU7X7D36OIEJRDDPLY X-Message-ID-Hash: SKR3IRAPPOD5AWSU7X7D36OIEJRDDPLY 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 Datacenter Manager development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Wed, 04 Feb 2026 16:27:20 +0100, Lukas Wagner wrote: > If ParallelFetcher is used in a worker task, we need to ensure to > inherit the log context from the current task, otherwise log messages > printed in the handler function are not printed to the task log. > > Applied, thanks! FWIW, shoukd this be a more frequent pattern, we might want to add a current_scope fn to LogContext that is the same as the scope fn, but wraps it transparently into a future in the current log context or the one passed as parameter. [2/5] parallel fetcher: make sure to inherit log context commit: c1f3c4a4ad253a1c620941f4bd7eee8ce581ecba