Repository navigation
feat: probe a tz link TZID and a task start without a due - #62
Merged
Merged
Conversation
Bedework 5 refuses an event in Europe/Oslo, a link to Europe/Berlin since tzdata 2022b, with 403 "unknownTimezone", even with a matching VTIMEZONE. The new probe stores one with its VTIMEZONE and grades save-load.icalendar.tzid-link: full when kept, quirk when stored as Europe/Berlin, unsupported when another TZID comes back, ungraceful when refused. The last two count only where the same event in Europe/Berlin is stored, and in the unsupported case read back as Europe/Berlin, so a server renaming every TZID says nothing. Bedework 5 comes out ungraceful, Bedework 3 and Baikal full; the TODO entry had seen the refusal on Bedework 3 on 2026-10-26, which this probe does not reproduce. The entry goes. Its "without VTIMEZONE" variant is left out on purpose: a TZID with no VTIMEZONE is what save-load.icalendar.olson-tzid probes. The entry pointed at #39, the vtimezone probe, which is closed. Prompt: ... continue working on getting all the conformance tests passing [in calendaring-client] Followup-Prompt: Go with [a caldav-server-tester probe, a caldav hint, and caldav rewriting a tz link name to its canonical zone before saving] Assisted-By: Claude Opus 5.5 <noreply@anthropic.com> Reviewed-by: Tobias Brox <tobias@redpill-linpro.com>
Zimbra drops the DTSTART of a task that has no DUE, though RFC 5545 allows either alone, and keeps both where there is a DUE. The new probe stores such a task and grades save-load.todo.dtstart-without-due; where the DTSTART is dropped, the same task with its DUE tells the two cases apart in the behaviour. Zimbra 10.1 comes out unsupported (kept with a DUE), Baikal full. Prompt: ... continue working on getting all the conformance tests passing [in calendaring-client] Followup-Prompt: [add] a tester probe and new caldav hint [for the Zimbra behaviour of dropping a task's DTSTART without a DUE] Assisted-By: Claude Opus 5.5 <noreply@anthropic.com> Reviewed-by: Tobias Brox <tobias@redpill-linpro.com>
With filterwarnings = ["error"], a system-wide pytest-asyncio turns its "asyncio_default_fixture_loop_scope is unset" deprecation warning into a fatal error. Setting that option instead would make pytest without the plugin (as in CI) fail on an unknown config option, so disable the plugin; there are no async tests. Prompt: Check tmp-handover-2026-11-15T125003-197a233b.md - add the asyncio_default_fixture_loop_scope fix to pyproject.toml in the PR#62. I will push it manually, no need with a full review procedure for this [the handover file is a session note; PR#62 is #62] Assisted-By: Claude Opus 5.5 <noreply@anthropic.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.
Disclaimer: AI-generated code and text below the line, generated by Claude Opus 5.5, from the prompts:
Two new probes, matching the hints in python-caldav/caldav#869. Until a caldav release defines the features, the tester carries their definitions itself.
save-load.icalendar.tzid-link: whether an event whose TZID is a tz database link name (Europe/Oslo), sent with its VTIMEZONE, is stored with that TZID. Bedework 5 refuses it with 403unknownTimezone(ungraceful); Bedework 3 and Baikal come out full.save-load.todo.dtstart-without-due: whether a task with a DTSTART and no DUE keeps its DTSTART. Zimbra 10.1 drops it, though it keeps it beside a DUE (unsupported); Baikal comes out full.The commits carry the details.
🤖 Generated with Claude Code