From 33e2c6a55eca94c59e5c818fd87bbb80176ea03e Mon Sep 17 00:00:00 2001 From: Mathias Gumz Date: Sun, 9 Nov 2025 22:05:54 +0100 Subject: [PATCH] fix: fix hard stop when facing 404 resources on the server Everyone's darling Google-Caldav server might reference resources which, in the end, do not exist: debug: /caldav/v2/user@example.com/events/_60q30c1g60o...@google.com.ics debug: HTTP/1.1 404 Not Found This situation leads to an unconditional hard stop of processing all the other, valid and available calendar entries: error: Unknown error occurred for my_sync/user@example.com: /caldav/v2/user@example.com/events/_60q30c1g60o...@google.com.ics error: Use `-vdebug` to see the full traceback. Instead of a hard stop, this commit changes the behaviour of vdirsyncer to just print a warning and continue. --- vdirsyncer/storage/dav.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vdirsyncer/storage/dav.py b/vdirsyncer/storage/dav.py index fcf5ae07..cd35020f 100644 --- a/vdirsyncer/storage/dav.py +++ b/vdirsyncer/storage/dav.py @@ -550,7 +550,7 @@ async def get_multi(self, hrefs): else: rv.append((href, Item(raw), etag)) for href in hrefs_left: - raise exceptions.NotFoundError(href) + dav_logger.warning(f"Server does not have referenced item: {href}") for href, item, etag in rv: yield href, item, etag