]> git.proxmox.com Git - pve-manager.git/commit
projects / pve-manager.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 17e852a) | patch
ui: qemu: stop pending changes in correct scope
authorThomas Lamprecht <t.lamprecht@proxmox.com>
Fri, 22 May 2020 15:16:35 +0000 (17:16 +0200)
committerThomas Lamprecht <t.lamprecht@proxmox.com>
Fri, 22 May 2020 15:16:37 +0000 (17:16 +0200)
commit433645160f8e216884bb23e3e1d49886114382ec
tree82b4cf9b6567ef21a2139d6333da9703f320cbd1tree
parent17e852abce323e41627f9ca6f65fe334dd90278ccommit | diff
ui: qemu: stop pending changes in correct scope

I saw some cases where the pending changes just continued to get
triggered for some VMs, even if they shouldn't anymore - effectively
resulting in 3 - 4 concurrent pending changes call at a time.

It could be this, or not, but it's cleaner this way so go for it

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
www/manager6/qemu/Options.js diff | blob | blame | history
The Proxmox VE Management API and Web UI