Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Searching also returns full-day events of adjacent days

Abierto
  • ¿Algo no está bien?
#545 6 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
python
Área
api

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
412
Forks
113
Merge medio
1 d 6 h
PR fusionados (30 d)
35

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de python-caldav/caldav

Todos los issues de python-caldav/caldav

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.