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 23ED41FF15C for ; Fri, 14 Nov 2025 22:09:58 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6E0C71B2C3; Fri, 14 Nov 2025 22:09:58 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Dominik Csapak Date: Fri, 14 Nov 2025 22:09:03 +0100 Message-ID: <176315454166.132706.4921685914795273798.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20251114145927.3766668-2-d.csapak@proxmox.com> References: <20251114145927.3766668-1-d.csapak@proxmox.com> <20251114145927.3766668-2-d.csapak@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1763154568362 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.023 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 pve-apiclient v4 1/1] try to refresh ticket before an api call 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" On Fri, 14 Nov 2025 15:59:16 +0100, Dominik Csapak wrote: > when the ticket is an hour old (or older). > This can help for long running tasks that reuse the api client > throughout the whole task. > > It will not work though if there is more than 2 hours between api calls, > but that should not be the case that often. > > [...] Applied, thanks! I reworked the code slightly in a few small follow-ups and also tried to improve how api-tokens are handled to avoid that a user needs to care about prefixing PVEApiToken. [1/1] try to refresh ticket before an api call commit: 083a9447df8da2fb5c26c6eb4d588d60a12d58c6 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel