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 9283D1FF13A for ; Wed, 01 Apr 2026 10:01:13 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D207211E7C; Wed, 1 Apr 2026 10:00:51 +0200 (CEST) From: Arthur Bied-Charreton To: pve-devel@lists.proxmox.com Subject: [PATCH pve-manager v2 15/17] ui: VMCPUFlagSelector: Allow filtering out flags supported on 0 nodes Date: Wed, 1 Apr 2026 10:00:26 +0200 Message-ID: <20260401080028.62513-16-a.bied-charreton@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260401080028.62513-1-a.bied-charreton@proxmox.com> References: <20260401080028.62513-1-a.bied-charreton@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.116 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 KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Message-ID-Hash: 4ODMJA4YXKUINTO6X6GBU7CAAFCZYRM2 X-Message-ID-Hash: 4ODMJA4YXKUINTO6X6GBU7CAAFCZYRM2 X-MailFrom: abied-charreton@jett.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: The cpu-flags endpoints may return some CPU flags that are not supported on any node in the cluster. Filter those out by default in the UI, giving the option to display them via a checkbox. Unknown flags are still shown at the top of the list. Signed-off-by: Arthur Bied-Charreton --- www/manager6/form/VMCPUFlagSelector.js | 33 ++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/www/manager6/form/VMCPUFlagSelector.js b/www/manager6/form/VMCPUFlagSelector.js index cbd6e2c7..765d325d 100644 --- a/www/manager6/form/VMCPUFlagSelector.js +++ b/www/manager6/form/VMCPUFlagSelector.js @@ -340,6 +340,39 @@ Ext.define('PVE.form.VMCPUFlagSelector', { }, ]; + me.dockedItems.push({ + xtype: 'toolbar', + dock: 'bottom', + items: [ + { + xtype: 'checkbox', + checked: true, + submitValue: false, + isFormField: false, + boxLabel: gettext('Only show flags supported by at least one node'), + listeners: { + change: function (cb, checked) { + let store = cb.up('grid').getStore(); + if (checked) { + store.addFilter({ + id: 'supported-filter', + filterFn: (rec) => { + if (rec.get('unknown')) { + return true; + } + let s = rec.get('supported-on'); + return Array.isArray(s) && s.length > 0; + }, + }); + } else { + store.removeFilter('supported-filter'); + } + }, + }, + }, + ], + }); + me.callParent(arguments); me.initialized = true; -- 2.47.3