public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Daniel Kral <d.kral@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager 7/7] ui: cpu flag selector: query CPU flag list via API
Date: Fri, 7 Nov 2025 10:30:06 +0100	[thread overview]
Message-ID: <9699332f-a6f8-4e70-b5df-b4e17ccfd493@proxmox.com> (raw)
In-Reply-To: <DE1RRET4YD8L.3J4SE4C6DO6CQ@proxmox.com>

Am 06.11.25 um 5:57 PM schrieb Daniel Kral:
> On Fri Oct 31, 2025 at 1:27 PM CET, Fiona Ebner wrote:
>>          // ExtJS does not has a nice getAllRecords interface for stores :/
>>          store.queryBy(Ext.returnTrue).each(function (rec) {
> 
> unrelated to the patch, but shouldn't `store.getData()` return all the
> records? `store.getData().getSource()` would be the equivalent, but as
> the store for cpu capabilities isn't filtered right now, the former
> should work.

I'll check it out for v2.

>> +    setValue: function (value) {
>> +        let me = this;
>> +
>> +        me.value = value || '';
>> +
>> +        if (me.getStore().isLoaded()) {
>> +            me.adjustForValue();
> 
> Shouldn't this be `me.adjustStoreForValue();`? :)

Good catch!

> I haven't yet found a way to trigger this though - neither in the Create
> wizard nor the CPU modal with and without values - but maybe my
> debugging strategy here is a bit wrong. How did you trigger it?

I did not actually manage to trigger it either. I'm not sure it can even
happen in practice right now. It makes sense for future-proofing, but I
missed adapting to the last rename of the function I did.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2025-11-07  9:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31 12:27 [pve-devel] [PATCH-SERIES qemu-server/manager 0/7] VM CPU flags: introduce vendor-agnostic 'nested-virt' CPU flag Fiona Ebner
2025-10-31 12:27 ` [pve-devel] [PATCH qemu-server 1/7] cpu config: style fix: avoid multiline post-if expressions Fiona Ebner
2025-11-06 18:03   ` [pve-devel] applied: " Thomas Lamprecht
2025-10-31 12:27 ` [pve-devel] [PATCH qemu-server 2/7] cpu config: style fix: avoid overly long ternary conditional expression Fiona Ebner
2025-11-06 18:03   ` [pve-devel] applied: " Thomas Lamprecht
2025-10-31 12:27 ` [pve-devel] [PATCH qemu-server 3/7] api: add endpoint for querying available cpu flags Fiona Ebner
2025-11-06 18:02   ` Thomas Lamprecht
2025-11-06 18:17     ` Thomas Lamprecht
2025-11-07  9:05     ` Fiona Ebner
2025-10-31 12:27 ` [pve-devel] [PATCH qemu-server 4/7] cpu config: introduce vendor-agnostic 'nested-virt' CPU flag Fiona Ebner
2025-11-06 17:00   ` Daniel Kral
2025-11-07  9:12     ` Fiona Ebner
2025-10-31 12:27 ` [pve-devel] [PATCH manager 5/7] api: capabilities: register module for VM CPU flags Fiona Ebner
2025-10-31 12:27 ` [pve-devel] [PATCH manager 6/7] ui: cpu flag selector: code style: use 'let' for declarations Fiona Ebner
2025-10-31 12:27 ` [pve-devel] [PATCH manager 7/7] ui: cpu flag selector: query CPU flag list via API Fiona Ebner
2025-11-06 16:57   ` Daniel Kral
2025-11-07  9:30     ` Fiona Ebner [this message]
2025-11-06 17:13 ` [pve-devel] [PATCH-SERIES qemu-server/manager 0/7] VM CPU flags: introduce vendor-agnostic 'nested-virt' CPU flag Daniel Kral
2025-11-07 11:33   ` Fiona Ebner
2025-11-07 12:13     ` Daniel Kral

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9699332f-a6f8-4e70-b5df-b4e17ccfd493@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=d.kral@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal