From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 0C5AD1FF0AA for ; Tue, 17 Nov 2026 10:35:48 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id AE9FB215F7; Tue, 17 Nov 2026 10:35:44 +0100 (CET) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Tue, 17 Nov 2026 10:35:41 +0100 Message-Id: Subject: Re: [PATCH many 00/55] notify: maintenance, PDM preparations, queue + worker From: "Lukas Wagner" To: "Lukas Wagner" , X-Mailer: aerc 0.22.0-0-gc2f86b7abde3 References: <20261113150828.756836-1-l.wagner@proxmox.com> In-Reply-To: <20261113150828.756836-1-l.wagner@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794908141246 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.202 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: 5NFE6LDCVITUGMFX4R76NTMJ52QWRDWV X-Message-ID-Hash: 5NFE6LDCVITUGMFX4R76NTMJ52QWRDWV X-MailFrom: l.wagner@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 Nov 13, 2026 at 4:07 PM CET, Lukas Wagner wrote: > The notification stack will soon be integrated into a new product (PDM), = so it > makes sense to use this opportunity for any pending breaking changes and > general cleanup of the notification stack, partly driven by the worker > implementation, pending feature work (notification history), and overdue > maintenance work to reduce technical debt. > > The introduction of a shared worker implementation lifts long-standing li= mitations in PVE, > where only the privileged process could send notifications. The worker wi= ll also be used > in PDM. > Will send a v2 soon with a couple of fixes, was made aware of an issue that must be fixed before applying this.