From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
Cc: Lukas Wagner <l.wagner@proxmox.com>,
pbs-devel@lists.proxmox.com, pve-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox 10/29] notify: matcher: add InlineCalendarMatcher
Date: Fri, 24 Jul 2026 11:43:34 +0200 [thread overview]
Message-ID: <vdbumk45y2yxv347wwgjipiei6un2zm63egrjkf2jc7g4x3ryo@wumelmkhydy4> (raw)
In-Reply-To: <ckq6k6ozmfccevtzfevcs35soxafhmujxwrwlacekq4mkbwjsr@7ka37aj4v7mz>
On Fri, Jul 24, 2026 at 08:47:00AM +0200, Arthur Bied-Charreton wrote:
> On Thu, Jul 09, 2026 at 01:56:57PM +0200, Lukas Wagner wrote:
> > This move the inline serialization format into a new-type wrapper around
> > CalendarMatcher.
> >
> > This allows us to keep the existing single-line serialization format for
> > the old configuration keys (match-calendar), while deriving a regular
> > Serializer for CalendarMatcher that will be used in the new expression
> > based matcher.
> >
> one comment inline
> > Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
> > ---
> > proxmox-notify/src/matcher/calendar.rs | 103 +++++++++++++++++++++----
> > proxmox-notify/src/matcher/mod.rs | 4 +-
> > 2 files changed, 88 insertions(+), 19 deletions(-)
> >
> > diff --git a/proxmox-notify/src/matcher/calendar.rs b/proxmox-notify/src/matcher/calendar.rs
> > index 970801c5..c6263eb5 100644
> > --- a/proxmox-notify/src/matcher/calendar.rs
> > +++ b/proxmox-notify/src/matcher/calendar.rs
> > @@ -1,49 +1,104 @@
> > use std::fmt;
> > use std::str::FromStr;
> >
> > +use serde::{Deserialize, Serialize};
> > +
> > use proxmox_time::DailyDuration;
> >
> > use crate::{Error, Notification};
> >
> > use super::MatchDirective;
> >
> > -/// Match timestamp of the notification.
> > +/// Convenience wrapper around [`DailyDuration`] that implements [`Serialize`] and
> > +/// [`Deserialize`].
> > #[derive(Clone, Debug)]
> > +struct DailyDurationWrapper {
> > + schedule: String,
> > + daily_duration: DailyDuration,
> > +}
> > +
> > +impl fmt::Display for DailyDurationWrapper {
> > + fn fmt(&self, f: &mut fmt::Formatter) -> fmt::Result {
> > + f.write_str(self.as_str())
> > + }
> > +}
> > +
> > +impl FromStr for DailyDurationWrapper {
> > + type Err = Error;
> > +
> > + fn from_str(s: &str) -> Result<Self, Error> {
> > + let daily_duration = proxmox_time::parse_daily_duration(s)
> we might wanna trim s here? this fails if s has a leading whitespace,
> which is a code path reachable via the UI (see [0]), and even if/when
> that is fixed, i feel like it would be nicer to not fail to parse
> because of surrounding whitespace (could also be done at another level
> of the call stack), since that would still be reachable via pvesh etc.
I would avoid allowing white space in the `FromStr` implementation and
prefer to keep the responsibility here with the caller, to stay
consistent with other `FromStr` implementations. (Eg. the std lib fails
to parse " 33" or "33 " as an `usize`.)
>
> [0] https://lore.proxmox.com/pve-devel/20260709115716.299836-1-l.wagner@proxmox.com/T/#mad9286504ecf2264333be5abe8b9e1f4966aeaeb
> > + .map_err(|e| Error::Generic(format!("could not parse schedule: {e}")))?;
> > +
> > + Ok(Self {
> > + daily_duration,
> > + schedule: s.to_string(),
> > + })
> > + }
> > +}
> > +
> > +impl DailyDurationWrapper {
> > + fn as_str(&self) -> &str {
> > + &self.schedule
> > + }
> > +}
> > +
> > +proxmox_serde::forward_deserialize_to_from_str!(DailyDurationWrapper);
> > +proxmox_serde::forward_serialize_to_display!(DailyDurationWrapper);
> > +
> > +/// Match timestamp of the notification.
> > +#[derive(Clone, Debug, Serialize, Deserialize)]
> > +#[serde(rename_all = "kebab-case")]
> > pub struct CalendarMatcher {
> > - schedule: DailyDuration,
> > - original: String,
> > + schedule: DailyDurationWrapper,
> > }
> >
> > impl MatchDirective for CalendarMatcher {
> > fn matches(&self, notification: &Notification) -> Result<bool, Error> {
> > self.schedule
> > + .daily_duration
> > .time_match(notification.metadata.timestamp, false)
> > .map_err(|err| Error::Generic(format!("could not match timestamp: {err}")))
> > }
> > }
> >
> > -impl fmt::Display for CalendarMatcher {
> > - fn fmt(&self, f: &mut fmt::Formatter) -> fmt::Result {
> > - f.write_str(&self.original)
> > +/// Match the timestamp of a notification.
> > +///
> > +/// This is a wrapper that serializes into an inline format that can be used
> > +/// in a section config key-value pair.
> > +#[derive(Clone, Debug)]
> > +pub struct InlineCalendarMatcher(CalendarMatcher);
> > +
> > +impl MatchDirective for InlineCalendarMatcher {
> > + fn matches(&self, notification: &Notification) -> Result<bool, Error> {
> > + self.0.matches(notification)
> > }
> > }
> >
> > -impl FromStr for CalendarMatcher {
> > +impl fmt::Display for InlineCalendarMatcher {
> > + fn fmt(&self, f: &mut fmt::Formatter) -> fmt::Result {
> > + f.write_str(self.0.schedule.as_str())
> > + }
> > +}
> > +
> > +impl FromStr for InlineCalendarMatcher {
> > type Err = Error;
> >
> > fn from_str(s: &str) -> Result<Self, Error> {
> > - let schedule = proxmox_time::parse_daily_duration(s)
> > - .map_err(|e| Error::Generic(format!("could not parse schedule: {e}")))?;
> > -
> > - Ok(Self {
> > - schedule,
> > - original: s.to_string(),
> > - })
> > + Ok(Self(CalendarMatcher {
> > + schedule: s.parse()?,
> > + }))
> > }
> > }
> >
> > -proxmox_serde::forward_deserialize_to_from_str!(CalendarMatcher);
> > -proxmox_serde::forward_serialize_to_display!(CalendarMatcher);
> > +impl InlineCalendarMatcher {
> > + pub fn into_inner(self) -> CalendarMatcher {
> > + self.0
> > + }
> > +}
> > +
> > +proxmox_serde::forward_deserialize_to_from_str!(InlineCalendarMatcher);
> > +proxmox_serde::forward_serialize_to_display!(InlineCalendarMatcher);
> >
> > #[cfg(test)]
> > mod test {
> > @@ -63,7 +118,21 @@ mod test {
> >
> > // Match on a wide rage to avoid issues when running this test case
> > // in a different time zone.
> > - let matcher: CalendarMatcher = "thu..sat 0-23".parse().unwrap();
> > + let matcher: InlineCalendarMatcher = "thu..sat 0-23".parse().unwrap();
> > assert!(matcher.matches(¬ification).unwrap());
> > }
> > +
> > + #[test]
> > + fn test_calendar_matcher_de_ser_roundtrip() {
> > + let calendar_matcher = "{ \"schedule\": \"thu..sat 0-23\" }";
> > +
> > + let calendar_matcher: CalendarMatcher = serde_json::from_str(calendar_matcher).unwrap();
> > +
> > + let s = serde_json::to_string(&calendar_matcher).unwrap();
> > + let m: CalendarMatcher = serde_json::from_str(&s).unwrap();
> > +
> > + let a = InlineCalendarMatcher(m);
> > +
> > + assert_eq!(a.to_string(), "thu..sat 0-23");
> > + }
> > }
> > diff --git a/proxmox-notify/src/matcher/mod.rs b/proxmox-notify/src/matcher/mod.rs
> > index 0267a2b9..a5d53d8a 100644
> > --- a/proxmox-notify/src/matcher/mod.rs
> > +++ b/proxmox-notify/src/matcher/mod.rs
> > @@ -14,7 +14,7 @@ pub mod calendar;
> > pub mod field;
> > pub mod severity;
> >
> > -use calendar::CalendarMatcher;
> > +use calendar::InlineCalendarMatcher;
> > use field::InlineFieldMatcher;
> > use severity::InlineSeverityMatcher;
> >
> > @@ -112,7 +112,7 @@ pub struct MatcherConfig {
> > /// List of matched severity levels.
> > #[serde(default, skip_serializing_if = "Vec::is_empty")]
> > #[updater(serde(skip_serializing_if = "Option::is_none"))]
> > - pub match_calendar: Vec<CalendarMatcher>,
> > + pub match_calendar: Vec<InlineCalendarMatcher>,
> > /// Decide if 'all' or 'any' match statements must match.
> > #[serde(skip_serializing_if = "Option::is_none")]
> > pub mode: Option<MatchModeOperator>,
> > --
> > 2.47.3
next prev parent reply other threads:[~2026-07-24 9:44 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 11:56 [PATCH many 00/29] notifications: add nested match expressions Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 01/29] add new proxmox-match-expression crate Lukas Wagner
2026-07-24 6:46 ` Arthur Bied-Charreton
2026-07-09 11:56 ` [PATCH proxmox 02/29] notify: promote matcher to dir-style module Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 03/29] notify: fix doc comment Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 04/29] notify: matcher: break out severity matcher into submodule Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 05/29] notify: matcher: break out field " Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 06/29] notify: matcher: break out calendar " Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 07/29] notify: matcher: calendar: add basic unit test Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 08/29] notify: matcher: add InlineSeverityMatcher Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 09/29] notify: matcher: add InlineFieldMatcher Lukas Wagner
2026-07-09 11:56 ` [PATCH proxmox 10/29] notify: matcher: add InlineCalendarMatcher Lukas Wagner
2026-07-24 6:47 ` Arthur Bied-Charreton
2026-07-24 9:43 ` Wolfgang Bumiller [this message]
2026-07-09 11:56 ` [PATCH proxmox 11/29] notify: matcher: add expression support Lukas Wagner
2026-07-24 6:59 ` Arthur Bied-Charreton
2026-07-24 8:27 ` PVE::Cluster::cfs_lock_domain - bizarre issue Anthony Galica
2026-07-24 9:38 ` :Cluster::cfs_lock_domain " Anthony Galica
2026-07-25 7:14 ` Anthony Galica
2026-07-09 11:56 ` [PATCH proxmox 12/29] notify: api: support new expression parameter Lukas Wagner
2026-07-24 6:46 ` Arthur Bied-Charreton
2026-07-24 10:01 ` Wolfgang Bumiller
2026-07-24 11:38 ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox 13/29] notify: api: add `get_matcher_as_expression` Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox 14/29] notify: migrate PBS's and PVE's default matcher to expression syntax Lukas Wagner
2026-07-24 6:47 ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox 15/29] notify: move legacy matcher keys behind feature flag Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-widget-toolkit 16/29] notification: increase matcher window width Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-widget-toolkit 17/29] notifications: matcher: add support for match expressions Lukas Wagner
2026-07-24 6:45 ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox-widget-toolkit 18/29] notification: matcher: add better calendar editor Lukas Wagner
2026-07-24 6:46 ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox-widget-toolkit 19/29] notifications: matcher: consistently use title case for UI elements Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-backup 20/29] notification: opt into 'legacy-matchers' feature in proxmox-notify Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-backup 21/29] api: notification: add 'migrate-to-expression' parameter to get_matcher Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-backup 22/29] ui: notification: enable new matcher UI Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-perl-rs 23/29] notify: matcher: pass matcher config / updater directly Lukas Wagner
2026-07-09 11:57 ` [PATCH proxmox-perl-rs 24/29] notify: opt into 'legacy-matchers' feature in proxmox-notify Lukas Wagner
2026-07-24 6:48 ` Arthur Bied-Charreton
2026-07-09 11:57 ` [PATCH proxmox-perl-rs 25/29] notify: add 'migrate_to_expression' parameter for get_matcher Lukas Wagner
2026-07-09 11:57 ` [PATCH manager 26/29] api: notification: pass config/updater directly to rust bindings Lukas Wagner
2026-07-09 11:57 ` [PATCH manager 27/29] api: notification: get_matcher: add 'migrate-to-expression' parameter Lukas Wagner
2026-07-09 11:57 ` [PATCH manager 28/29] api: notification: add 'expression' to matcher parameter schema Lukas Wagner
2026-07-09 11:57 ` [PATCH manager 29/29] ui: notification: enable new matcher UI Lukas Wagner
2026-07-24 6:44 ` [PATCH many 00/29] notifications: add nested match expressions Arthur Bied-Charreton
2026-07-24 6:53 ` Arthur Bied-Charreton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vdbumk45y2yxv347wwgjipiei6un2zm63egrjkf2jc7g4x3ryo@wumelmkhydy4 \
--to=w.bumiller@proxmox.com \
--cc=a.bied-charreton@proxmox.com \
--cc=l.wagner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox