From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
	by lore.proxmox.com (Postfix) with ESMTPS id 080611FF183
	for <inbox@lore.proxmox.com>; Wed,  4 Jun 2025 13:11:39 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 983E63A755;
	Wed,  4 Jun 2025 13:11:56 +0200 (CEST)
Message-ID: <5aeb91d1-8cdf-4a9b-b0d2-b080a44fb0f3@proxmox.com>
Date: Wed, 4 Jun 2025 13:11:52 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird Beta
To: pve-devel@lists.proxmox.com
References: <20250603145643.243019-1-s.shaji@proxmox.com>
Content-Language: en-US
From: Dominik Csapak <d.csapak@proxmox.com>
In-Reply-To: <20250603145643.243019-1-s.shaji@proxmox.com>
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.022 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
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
Subject: [pve-devel] applied: [PATCH
 proxmox_dart_api_client/pve_flutter_frontend 0/2] fix: ui: `unknown` status
 shown when the QEMU state is `prelaunch`
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>

On 6/3/25 16:56, Shan Shaji wrote:
> This patch series fixes an issue where the VM status was
> shown as `unknown` when the QEMU state is `prelaunch`. Additionaly,
> also fixes the resume option missing inside the power settings sheet
> when the QEMU state is `prelaunch`.
> 
> Steps to reproduce:
>    - Select any VM
>    - Go to the options tab.
>    - Enable "Freeze CPU at startup"
>    - Start the VM on web UI
>    - Go to mobile app ui and check the status of the VM
>      on the resources tab and on the VM overview page.
>      The status will be `unknown`.
>    - Now on the VM overview page click on the `power settings`
>      option on the app UI. The resume option is not shown.
> 
> pve_flutter_frontend:
> 
> Shan Shaji (1):
>    fix: qemu: `unknown` status shown when VM is in `prelaunch` status
> 
>   lib/widgets/pve_qemu_power_settings_widget.dart  | 3 ++-
>   lib/widgets/pve_resource_status_chip_widget.dart | 3 +++
>   2 files changed, 5 insertions(+), 1 deletion(-)
> 
> 
> proxmox_dart_api_client:
> 
> Shan Shaji (1):
>    fix: add missing `prelaunch` value to `PveResourceStatusType`
> 
>   lib/src/models/pve_cluster_resources_model.dart | 3 +++
>   lib/src/models/pve_nodes_qemu_status_model.dart | 2 ++
>   2 files changed, 5 insertions(+)
> 
> 
> Summary over all repositories:
>    4 files changed, 10 insertions(+), 1 deletions(-)
> 


applied series, thanks!


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