From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id EB53F9E53B for ; Mon, 27 Nov 2023 14:31:17 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id CD9478054 for ; Mon, 27 Nov 2023 14:31:17 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Mon, 27 Nov 2023 14:31:16 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 98D0544B54 for ; Mon, 27 Nov 2023 14:31:16 +0100 (CET) Date: Mon, 27 Nov 2023 14:12:45 +0100 From: Fabian =?iso-8859-1?q?Gr=FCnbichler?= To: Proxmox Backup Server development discussion References: <20231109153403.529870-1-s.sterz@proxmox.com> <20231109153403.529870-3-s.sterz@proxmox.com> In-Reply-To: <20231109153403.529870-3-s.sterz@proxmox.com> MIME-Version: 1.0 User-Agent: astroid/0.16.0 (https://github.com/astroidmail/astroid) Message-Id: <1701090677.0woujpape4.astroid@yuna.none> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL 0.064 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 T_SCC_BODY_TEXT_LINE -0.01 - URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com] Subject: [pbs-devel] applied: [PATCH proxmox 2/6] subscription: expose the `next_due_date` as an `i64` X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Nov 2023 13:31:18 -0000 On November 9, 2023 4:33 pm, Stefan Sterz wrote: > internally `SubscriptionInfo` already uses the `parse_next_due` helper > to parse the next due date to an epoch. this exposes a function that > allows us to use the epoch outside of this crate too. for example, a > user of pom may have multiple subscription for the same system. in > that case we want to apply the one with the due date that is furthest > in the future. >=20 > Signed-off-by: Stefan Sterz > --- > proxmox-subscription/src/subscription_info.rs | 7 +++++++ > 1 file changed, 7 insertions(+) >=20 > diff --git a/proxmox-subscription/src/subscription_info.rs b/proxmox-subs= cription/src/subscription_info.rs > index dc10a2a..45f1796 100644 > --- a/proxmox-subscription/src/subscription_info.rs > +++ b/proxmox-subscription/src/subscription_info.rs > @@ -286,6 +286,13 @@ impl SubscriptionInfo { > .ok_or_else(|| format_err!("no product key set")) > .map(|key| key[..3].parse::())? > } > + > + pub fn get_next_due_date(&self) -> Result { > + self.nextduedate > + .as_ref() > + .ok_or_else(|| format_err!("no next due date set")) > + .map(|e| parse_next_due(e))? > + } > } >=20 > /// Shortcut for md5 sums. > -- > 2.39.2 >=20 >=20 >=20 > _______________________________________________ > pbs-devel mailing list > pbs-devel@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel >=20 >=20 >=20