From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 263791FF165 for ; Thu, 9 Oct 2025 11:33:22 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0CA5D1AA05; Thu, 9 Oct 2025 11:33:28 +0200 (CEST) Message-ID: <0d773f60-66e2-45a1-8345-36c992be019e@proxmox.com> Date: Thu, 9 Oct 2025 11:32:53 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta From: Dominik Csapak To: pdm-devel@lists.proxmox.com References: <20251008135558.3586369-1-d.csapak@proxmox.com> Content-Language: en-US In-Reply-To: <20251008135558.3586369-1-d.csapak@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1760002342152 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.028 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: Re: [pdm-devel] [RFC PATCH datacenter-manager 0/2] use streaming content api X-BeenThere: pdm-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Datacenter Manager development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Datacenter Manager development discussion Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: pdm-devel-bounces@lists.proxmox.com Sender: "pdm-devel" one thing i forgot to ask here is: how should we handle pbs3/4 compatibility? We have IMHO the following options: * Implement a fallback in the UI for pbs3 can be ok, we could duplicate the panel and drop the old one when pbs3 is not supported anymore? * Implement a fallback in the API for pbs3 most robust solution IMO, gui can stay mostly the same, code should not be that much, can also be dropped if we don't want to support pbs3 anymore * don't support pbs3 at all not really an option i think * also commit the changes to pbs stable-3 branch maybe the easiest way, but here's the question where we draw the line for older products regarding features/bugs/etc. On 10/8/25 3:56 PM, Dominik Csapak wrote: > instead of using the snapshot list + a namespace selector, use the > content api call [0] to show the whole tree. > > Sending as RFC because there are some crucial parts missing in the ui > (see the commit message of 2/2) but I wanted to get early feedback and > send out some patches so one can test the streaming content api call > in the pdm ui. > > 0: https://lore.proxmox.com/pbs-devel/20251008134344.3512958-1-d.csapak@proxmox.com/ > > Dominik Csapak (2): > server: add new streaming 'content' api call for pbs > ui: pbs: snapshot list: change to streaming 'content' api call > > server/src/api/pbs/mod.rs | 40 +++++++++- > server/src/pbs_client.rs | 51 +++++++++++++ > ui/src/pbs/snapshot_list.rs | 148 +++++++++++++++++++++++++----------- > 3 files changed, 193 insertions(+), 46 deletions(-) > _______________________________________________ pdm-devel mailing list pdm-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel