Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alarm search yields too many events #1266

Open
tobixen opened this issue Oct 24, 2022 · 0 comments
Open

Alarm search yields too many events #1266

tobixen opened this issue Oct 24, 2022 · 0 comments

Comments

@tobixen
Copy link
Contributor

tobixen commented Oct 24, 2022

I have this REPORT query (as per https://www.rfc-editor.org/rfc/rfc4791#section-7.8.5):

<C:calendar-query xmlns:D="DAV:" xmlns:C="urn:ietf:params:xml:ns:caldav">
  <D:prop>
    <C:calendar-data/>
  </D:prop>
  <C:filter>
    <C:comp-filter name="VCALENDAR">
      <C:comp-filter name="VEVENT">
        <C:comp-filter name="VALARM">
          <C:time-range start="20191010T060100Z" end="20191010T060700Z"/>
        </C:comp-filter>
      </C:comp-filter>
    </C:comp-filter>
  </C:filter>
</C:calendar-query>

And this event on the calendar:

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//python-caldav//caldav//en_DK
BEGIN:VEVENT
SUMMARY:This is a test event
DTSTART;VALUE=DATE-TIME:20151010T080706
DTEND;VALUE=DATE-TIME:20161010T090807
DTSTAMP;VALUE=DATE-TIME:20221024T143714Z
UID:96d4e74a-5398-11ed-a1df-a0510ba5c65c
BEGIN:VALARM
ACTION:AUDIO
TRIGGER:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR

The REPORT query does yield the above event, but it shouldn't (as the dates searched for is in 2019, while the alarm is in 2015).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant