Repository navigation
feat: probe task values, X- params and ghosts - #52
Merged
Merged
Conversation
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
force-pushed
the
feat/probes-group-b
branch
from
November 6, 2026 21:24
eda5b39 to
501f8df
Compare
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Needs the feature definitions of python-caldav/caldav#848 (merged, not yet released): the tester carries copies of them in
FUTURE_FEATURESuntil 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 modesandbuild: carry the features of caldav PR 848.