From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id 509921FF0B3 for ; Wed, 28 Oct 2026 16:09:41 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 58A00213D3; Wed, 28 Oct 2026 16:09:39 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Hannes Laimer Subject: applied: [PATCH pve-common] rest environment: start each worker task with a clean warning count Date: Wed, 28 Oct 2026 16:09:28 +0100 Message-ID: <179320016738.1381185.2808135691202397070.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260904072535.501236-1-h.laimer@proxmox.com> References: <20260904072535.501236-1-h.laimer@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: 1793200175116 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.492 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust 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: 5YUTHGE6XFP4IQ3AJHPC5UPN5G665C63 X-Message-ID-Hash: 5YUTHGE6XFP4IQ3AJHPC5UPN5G665C63 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 VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Fri, 04 Sep 2026 09:25:35 +0200, Hannes Laimer wrote: > The count lives in the per-process environment and is only reported by > a forked task at its end. A warning logged while handling a plain API > request stays counted, so every task the process forks afterwards ends > with WARNINGS although nothing in its log warned. Applied, thanks! [1/1] rest environment: start each worker task with a clean warning count commit: b9b41d526f1ee1c0424765e72af6181fff69f611