Skip to content

feat: probe whether the address set is populated - #16

Open
tobixen wants to merge 1 commit into
mainfrom
xandikos-empty-cuas
Open

tobixen wants to merge 1 commit into
mainfrom
xandikos-empty-cuas

Conversation

@tobixen

@tobixen tobixen commented Sep 20, 2026

Copy link
Copy Markdown
Member

CheckSchedulingDetails already fetched calendar-user-address-set and threw
the result away, so a server that serves the property but leaves it empty was
graded exactly like one that populates it. It now records the new
scheduling.calendar-user-address-set.populated, measured against live
Xandikos 0.4.7: unsupported.

The feature itself is defined in the companion caldav PR, python-caldav/caldav#716 — the two
belong together and have to be released together.

CI will be red on this branch, and it cannot be made green here: the check
asserts every configured feature is one the installed caldav knows, and this
one exists only in that branch. main is already red for the same reason
(auth.www-authenticate.usable-scheme, run 35495452947). pyproject.toml
still says caldav>=3.3.1; there is no released version to pin yet.

🤖 Generated with Claude Code

CheckSchedulingDetails already fetched calendar-user-address-set and
threw the result away, so a server that serves the property but leaves
it empty was graded exactly like one that populates it.  Xandikos 0.4.7
(or perhaps rather, the test user that the test container is populated
with?) serves it empty.  RFC 6638 section 2.4.1 says that the URI of the
principal resource should be used if the calendar user address is not
well-defined.  Measured against live Xandikos: 'unsupported'.

Prompt: Please fix [this check] in a new branch xandikos-empty-cuas on the caldav-server-tester project
[Some manual changes done during review process]

Assisted-By: Claude Opus 5 <noreply@anthropic.com>
Reviewed-by: Tobias Brox <tobias@redpill-linpro.com>
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