Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Searching also returns full-day events of adjacent days

Aperta
  • Qualcosa non va?
#545 6 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
python
Ambito
api

Direzione di ricerca

Start by reproducing the reported cases with the supplied calendar.search(start=..., end=..., event=True, expand=True) calls, then read the implementation and documentation for search() and its handling of full-day events and timezones. Done means searches return the expected events for the reported dates and timezone variants; clarify the intended CalDAV behavior before choosing a fix.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Problem:

I'm trying to find all events that occur today or later. In some cases, events from yesterday are returned.

I'm not completely sure if this is a bug or just the way CalDAV works, but at least it's not what I expected.

Test setup: There are there are three full-day events in the calendar, on 18.,19.,20.08.25. I created them with Thunderbird, the server is Baikal. I did not specify a timezone (nor could I for full-day events).

Code:

from datetime import datetime, timedelta, date, timezone
import caldav

url = "..."
username = "..."
password = "..."
client = caldav.DAVClient(url, username=username, password=password)
principal = client.principal()
calendars = principal.calendars()
calendar = next(cal for cal in calendars if cal.name == "Test-Cal")

# there are three full-day events in the calendar, on 18.,19.,20.08.25

dates = [
    datetime(year=2025, month=8, day=17, hour=0, minute=10),
    datetime(year=2025, month=8, day=17, hour=0, minute=10, tzinfo=timezone(timedelta(hours=2))),
    datetime(year=2025, month=8, day=17, hour=0, minute=10, tzinfo=timezone(timedelta(hours=0))),
    datetime(year=2025, month=8, day=17, hour=0, minute=0),
    datetime(year=2025, month=8, day=17, hour=0, minute=0, tzinfo=timezone(timedelta(hours=2))),
    datetime(year=2025, month=8, day=17, hour=0, minute=0, tzinfo=timezone(timedelta(hours=0))),
]

for test_time in dates:
    print("Testing with", test_time)
    print("    | 18 | 19 | 20 |")
    for i in range(4):
        print(f" +{i} |", end="")
        t = test_time + timedelta(days=i)
        results = calendar.search(start=t, end=t + timedelta(days=1), event=True, expand=True, sort_keys="dtstart")
        summaries = [e.instance.vevent.summary.value for e in results]
        for j in range(1, 4):
            if f"Test{j}" in summaries:
                print(f" X  |", end="")
            else:
                print(f"    |", end="")
        print()

Output (with comments from me). Expected would be a diagonal in the last three lines.

Testing with 2025-08-17 00:10:00 //my actual code, running in UTC+2 just after midnight
    | 18 | 19 | 20 |
 +0 |    |    |    |
 +1 | X  |    |    |
 +2 | X  | X  |    | //the bug I noticed
 +3 |    | X  | X  |
Testing with 2025-08-17 00:10:00+02:00 //add the timezone explicitly
    | 18 | 19 | 20 |
 +0 |    |    |    |
 +1 | X  |    |    |
 +2 | X  | X  |    | //no change
 +3 |    | X  | X  |
Testing with 2025-08-17 00:10:00+00:00 //now in UTC
    | 18 | 19 | 20 |
 +0 | X  |    |    | //this is correct b/c 00:10+1d contains the next day!
 +1 | X  | X  |    |
 +2 |    | X  | X  |
 +3 |    |    | X  |
Testing with 2025-08-17 00:00:00 // test on exactly midnight
    | 18 | 19 | 20 |
 +0 |    |    |    |
 +1 | X  |    |    |
 +2 | X  | X  |    | //same problem
 +3 |    | X  | X  |
Testing with 2025-08-17 00:00:00+02:00
    | 18 | 19 | 20 |
 +0 |    |    |    |
 +1 | X  |    |    |
 +2 | X  | X  |    | //dito
 +3 |    | X  | X  |
Testing with 2025-08-17 00:00:00+00:00 //midnight, UTC
    | 18 | 19 | 20 |
 +0 |    |    |    |
 +1 | X  |    |    | //correct!
 +2 |    | X  |    |
 +3 |    |    | X  |

This is the pattern I could make up from this:

  • without timezone infos, the datetime gets interpreted in the local timezone
  • before matching against full-day events in the calendar, dates are shifted to UTC
  • this causes the dates to move to the previous day

This is just my guesswork, someone with more insight to CalDAV can probably make more sense out of this.

Lingua principale
Python
Stelle
412
Fork
113
Merge medio
1g 2h
PR unite (30g)
41

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di python-caldav/caldav

Tutte le issue di python-caldav/caldav

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.