Skip to content

feat: probe task values, X- params and ghosts - #52

Merged
tobixen merged 3 commits into
mainfrom
feat/probes-group-b
Nov 6, 2026
Merged

tobixen merged 3 commits into
mainfrom
feat/probes-group-b

Conversation

@tobixen

@tobixen tobixen commented Nov 3, 2026 •

Copy link
Copy Markdown
Member

Needs the feature definitions of python-caldav/caldav#848 (merged, not yet released): the tester carries copies of them in FUTURE_FEATURES until a caldav release has them, so CI runs against the released caldav.

Commit message:

New probes for what the calendaring conformance suite found Ox and
Zimbra losing: every STATUS (with RFC 10051's PENDING and FAILED) and
every PRIORITY from 0 to 9 on a task, an X- parameter on SUMMARY in
an event and a task, and a multiget of an object just deleted. The
stable-url probe stores a task under another name too, since Ox
renames tasks .ics but not events.

Prompt: [fix the unmapped caldav hints, new caldav-server-tester checks and caldav profile updates now]

Assisted-By: Claude Opus 5.5 noreply@anthropic.com

Also on the branch: feat: probe RFC 10051 statuses and task modes and build: carry the features of caldav PR 848.

New probes for what the calendaring conformance suite found Ox and
Zimbra losing: every STATUS (with RFC 10051's PENDING and FAILED) and
every PRIORITY from 0 to 9 on a task, an X- parameter on SUMMARY in
an event and a task, and a multiget of an object just deleted.  The
stable-url probe stores a task under another name too, since Ox
renames tasks <uid>.ics but not events.

Prompt: [fix the unmapped caldav hints, new caldav-server-tester checks and caldav profile updates now]

Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-by: Tobias Brox <tobias@redpill-linpro.com>
A server need not keep PENDING and FAILED unless it supports RFC
10051, so they are swept apart from RFC 5545's four statuses, as
save-load.todo.status.rfc10051.  A new probe reads
CALDAV:supported-task-mode-set (RFC 10051 section 13.1), which says
whether a server claims that support; Ox and Zimbra do not, and the
RFC 10051 verdict then says so.  Ox now grades full on the RFC 5545
statuses.

Prompts (comments made inline in the document while reviewing it):
> (on the save-load.todo.status hint) Note for "save-load.todo.status" - a server may or may not support RFC 10051.  We can only demand it to support FAILED and PENDING if the server declares support for RFC 50051 (sic).  If there are many servers acceptign (sic) all the RFC 5545 statuses but not accepting FAILED and PENDING, then maybe we need to split out a child for the RFC 10051-statuses

Followup-Prompt: There exists a DAV-property in the RFC for querying for support as far as I remember.  The probe for it should be added in the caldav-server-tester as for now.  save-load.todo.status.rfc10051  is fine. (...) [the DAV property: CALDAV:supported-task-mode-set, RFC 10051 section 13.1]

Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-by: Tobias Brox <tobias@redpill-linpro.com>
The tester now defines the six features from caldav's merged but
unreleased python-caldav/caldav#848 in
FUTURE_FEATURES, copied from caldav's master: save-load.todo.status
and .rfc10051, save-load.todo.priority, supported-task-modes,
save-load.icalendar.x-parameter and multiget.deleted.  With them,
the tests pass against the released caldav 3.7.0 that CI installs;
60 of them failed without.  The CHANGELOG says so.

Prompt: Fix PR52, update or delete obsoleted memory notes.

Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-by: Tobias Brox <tobias@redpill-linpro.com>
@tobixen
tobixen force-pushed the feat/probes-group-b branch from eda5b39 to 501f8df Compare November 6, 2026 21:24
@tobixen
tobixen merged commit 63e8311 into main Nov 6, 2026
12 checks passed
tobixen added a commit that referenced this pull request Nov 7, 2026
The olson-tzid probe judged the server's reading of a bare TZID by a
time-range search, so a search that misplaces zoned times anyway was
graded as not understanding the TZID: Xandikos' index drops the TZID
once it answers a query, VTIMEZONE or not.  Where the bare TZID is not
placed in Tokyo, the probe now also stores the event with its
VTIMEZONE; if the search misplaces that too, the verdict is 'unknown'.

Prompt: (answer to a clarifying question) Merge 52; fix 54+850 (Recommended) [merge #52, then fix the probe and the hints after a review of python-caldav/caldav#850 showed Xandikos misplaces times in its search index whether or not the event has a VTIMEZONE]

Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-by: Tobias Brox <tobias@redpill-linpro.com>
tobixen added a commit that referenced this pull request Nov 7, 2026
python-caldav/caldav#850 was merged with a
sentence on 'fragile' (Xandikos' search path, Synology's web UI) added
to the description of save-load.icalendar.olson-tzid; the copy in
FUTURE_FEATURES now says the same.

Prompt: (answer to a clarifying question) Merge 52; fix 54+850 (Recommended) [merge #52, then fix the probe and the hints after the review of python-caldav/caldav#850]

Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewed-by: Tobias Brox <tobias@redpill-linpro.com>
@tobixen
tobixen deleted the feat/probes-group-b branch November 7, 2026 09:47
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

Successfully merging this pull request may close these issues.

1 participant