[pve-devel] [PATCH proxmox_login_manager] fix: ui: remove `SafeArea` to avoid black background in status bar

2025-05-15 Thread Shan Shaji
Since the `SafeArea` widget was wrapping the `Scaffold` widget, the background color of the status bar was black rather than influenced by the `AppBar` color. This patch fixes it by removing the `SafeArea` widget. According to flutter docs [0] when using `AppBar` with `Scaffold` the appropriate sp

[pve-devel] [PATCH common 1/1] sysfstools: make normalize_pci_id public

2025-05-15 Thread Dominik Csapak
so that we can use it from other modules/packages, such as qemu-server Signed-off-by: Dominik Csapak --- src/PVE/SysFSTools.pm | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/PVE/SysFSTools.pm b/src/PVE/SysFSTools.pm index f7acb9a..db0a607 100644 --- a/src/PVE/SysFST

[pve-devel] [PATCH qemu-server 1/1] fix #6400: pci: allow other pci domains than 0000 for NVIDIA vGPUs

2025-05-15 Thread Dominik Csapak
when creating or cleaning up NVIDIA vGPUs, we mistakenly assumed a PCI domain of , but this might be different. Use 'normalize_pci_id' from PVE::SysFSTools, which handles this already correctly. Signed-off-by: Dominik Csapak --- depends on the pve-common patch PVE/QemuServer.pm | 2 +-

[pve-devel] [PATCH common/qemu-server 0/2] fix #6400: allow pci domains other than 0000 for NVIDIA vGPUs

2025-05-15 Thread Dominik Csapak
by reusing the normalization of pci ids from SysFSTools qemu-server patch depends on a pve-common patch pve-common: Dominik Csapak (1): sysfstools: make normalize_pci_id public src/PVE/SysFSTools.pm | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) qemu-server: Dominik Csapak (1)

Re: [pve-devel] checking output of storage plugin API - volume_rollback_is_possible(..., blockers)

2025-05-15 Thread Fabian Grünbichler
> Andrei Perapiolkin hat am 15.05.2025 13:23 > CEST geschrieben: > > > Hi Fabian, > > > Thank you for detailed response. > > > out of interest - is your plugin publicly available? > > Yes, my plugin is available at https://github.com/open-e/JovianDSS-Proxmox > > Regarding blockers usage

[pve-devel] [PATCH pve_flutter_frontend] fix: ui: app bar text alignment issues in iOS

2025-05-15 Thread Shan Shaji
By default iOS centers the title in the appbar, which can create a visual inconsistency with the left aligned two line app name. Added a custom `PveAppBar` widget to maintain the design and alignment similliar to android. Also the new widget replaces all other `AppBar` widgets that has the title p

Re: [pve-devel] checking output of storage plugin API - volume_rollback_is_possible(..., blockers)

2025-05-15 Thread Andrei Perapiolkin via pve-devel
--- Begin Message --- Hi Fabian, Thank you for detailed response. out of interest - is your plugin publicly available? Yes, my plugin is available at https://github.com/open-e/JovianDSS-Proxmox Regarding blockers usage: https://github.com/open-e/JovianDSS-Proxmox/blob/22d0f7f8c4606d470a988

Re: [pve-devel] [PATCH pve-lxc-syscalld 2/4] service: avoid using generic runtime directory name

2025-05-15 Thread Thomas Lamprecht
Am 15.05.25 um 10:41 schrieb Fiona Ebner: > Am 14.05.25 um 16:33 schrieb Thomas Lamprecht: >> Am 13.05.25 um 12:56 schrieb Fiona Ebner: >>> When the service is restarted, the directory will be recreated. The >>> issue is that the /run/pve directory is not just used as the runtime >>> directory of t

Re: [pve-devel] checking output of storage plugin API - volume_rollback_is_possible(..., blockers)

2025-05-15 Thread Fabian Grünbichler
> Andrei Perapiolkin via pve-devel hat am > 14.05.2025 14:44 CEST geschrieben: > Hi, > > I'm trying to test specific aspects of the storage plugin API, > and I'm not sure how to verify whether my function > volume_rollback_is_possible > correctly sets up the blockers list. > > I've checked

Re: [pve-devel] [PATCH pve-lxc-syscalld 2/4] service: avoid using generic runtime directory name

2025-05-15 Thread Fiona Ebner
Am 14.05.25 um 16:33 schrieb Thomas Lamprecht: > Am 13.05.25 um 12:56 schrieb Fiona Ebner: >> When the service is restarted, the directory will be recreated. The >> issue is that the /run/pve directory is not just used as the runtime >> directory of this service, but also for other things, e.g. sto

[pve-devel] [PATCH proxmox-perl-rs] pve-rs: remove PVE::RS::APT:Repositories module

2025-05-15 Thread Hannes Duerr
We can remove the PVE::RS::APT::Repositories module because we needed its functionality in Proxmox VE and other products, so we moved it to Proxmox::RS::APT::Repositories some time ago. We now only use the new module in our code. When users update to Proxmox VE 9, we can be sure that there is no pa

Re: [pve-devel] [PATCH manager 1/4] add tpmfiles.d config to create /run/pve directory

2025-05-15 Thread Fiona Ebner
Am 14.05.25 um 20:08 schrieb Thomas Lamprecht: > Am 13.05.25 um 12:56 schrieb Fiona Ebner: >> The pve-lxc-syscalld systemd service currently uses /run/pve as a >> runtime directory. This means, that when the service is restarted, the >> directory will be recreated. But the /run/pve directory is not

[pve-devel] [PATCH widget-toolkit v2] fix #6312: limit consent window to viewport size

2025-05-15 Thread Dominik Csapak
The consent window will try to size itself according to the max/min constraints set, but those might be too large for some viewport sizes. Since it's not possible to set those to relative viewport sizes (ExtJS does it's own layout, so we can't use CSS), we have to save the original size and on res

Re: [pve-devel] [PATCH widget-toolkit] fix #6312: limit consent window to viewport size

2025-05-15 Thread Dominik Csapak
superseeded by v2: https://lore.proxmox.com/pve-devel/20250515080214.734035-1-d.csa...@proxmox.com/T/#u ___ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel