From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 2B0D21FF15E for ; Tue, 3 Jun 2025 16:56:59 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 272F71CD16; Tue, 3 Jun 2025 16:57:15 +0200 (CEST) From: Shan Shaji To: pve-devel@lists.proxmox.com Date: Tue, 3 Jun 2025 16:56:41 +0200 Message-Id: <20250603145643.243019-1-s.shaji@proxmox.com> X-Mailer: git-send-email 2.39.5 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.369 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. 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] [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" 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(-) -- Generated by git-murpp 0.8.1 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel