Recurring event with exclusions produce warnings
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.1k
- Forks
- 233
- Avg merge
- 1h 44m
- Merged PRs (30d)
- 1
Description
Describe the bug
I have en recurring event with many exclusions and it seems khal produces a warning for every exclusion:
warning: In event d215d83c-101b-4116-aed8-d481b8cdc47e.ics, excluded instance starting at 2025-06-05 09:30:00+02:00 not found, event might be invalid.
warning: In event d215d83c-101b-4116-aed8-d481b8cdc47e.ics, excluded instance starting at 2025-06-12 09:30:00+02:00 not found, event might be invalid.
...
To Reproduce
Use khal with the attached .ics file.
Expected behavior
If the .ics is invalid, the warning should be more detailed, so users understand what's the problem.
If the .ics is valid, khal should not produce a warning.
OS, version, khal version and how you installed it:
- The output of khal --version:
khal, version 0.13.0 - Installation method: Manjaro Arch package
- python version: 3.13.7
- OS: Arch (Manjaro)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the warnings in khal 0.13.0 with the attached d215d83c-101b-4116-aed8-d481b8cdc47e.ics file. Trace where excluded recurring instances are checked and warnings are emitted, then verify behavior for both valid and invalid calendar data. Done means valid input produces no warnings and invalid input reports a more detailed problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100