Am 01.08.25 um 18:58 schrieb Michael Köppl: > The goal of this is to refresh both affinity rules stores to > immediately display any conflicts. Without this change, users have to > refresh the page to see conflicts on resource affinity rules after they > added a node affinity rule that was in conflict (and vice-versa).
I went a bit of another route[0][1] that has also the advantage of not loading the same data twice which in turn also avoids not being potentially out-of-sync due to those twice loads returning a potentially different state. Thanks nonetheless for shining light to this issue, that was very helpful to me and allowed for some more code clean-ups–the original HA groups UI was a bit dated as it was added in 2015 where we did not used the more modern capabilities from ExtJS that allow a bit more declarative coding style by, e.g., encapsulating more logic to view controllers. [0]: https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=566ec7fdb80887cc59cd5b9946b44a7e747e2ad3 [1]: https://lore.proxmox.com/pve-devel/20250802172619.3692858-2-t.lampre...@proxmox.com/T/#u _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
