Florian Latifi

Okay, so I tested the prune job on my instance. I updated a calendar event on my Evolution client, synced it with Nextcloud which resulted in a new row in...

@Eskawotz Yeah, it seems to me that the prune job code is buggy. It did not keep any rows and wiped my `oc_calendarchanges` table. However, my second client (Dav5x) still...

The easiest way to disable this job without globally disabling cron for me seems to just comment all the code in the run function of `apps/dav/lib/BackgroundJob/PruneOutdatedSyncTokensJob.php`. ``` public function run($argument)...

For completeness, I digged deeper into the code, especially `CalDavBackend.php#getChangesForCalendar`. Missing rows in `oc_calendarchanges` will definitely affect clients that request calendar changes with a given sync token. They simply won't...

Nice! Thanks @charno for fixing the code and creating the PR :) Hoping for fast merge!

@joshtrichards I reverted the changes and simplified the code back to just print a one-line warning for every config file that differs. What do you think?

I myself got this warning today after updating to 28.0.7 :rofl: Will double-check my configs, but it seems the check fulfills its purpose :smile: If the confusion gets to big...

@joshtrichards I provided a PR in https://github.com/nextcloud/docker/pull/2120 that implements your suggested check in the Docker entrypoint. It prints a warning for every special config file that is missing in the...

Another false positive (LePresidente/http-generic-403-bf) I get is when synchronizing CalDAV calendars with Gnome Evolution 3.50. I also have to exclude HTTP POST requests resulting in 403 errors. Here are the...

Thank you for the hint and short-term fix using libxcrypt-compat. I noticed this issue with the Evolution extension of DecSync no longer loading after an Arch update. In the long...