Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Future events are not synchronized when past event time limit is set #920

Closed
2 tasks done
sunkup opened this issue Jul 18, 2024 · 2 comments
Closed
2 tasks done

Future events are not synchronized when past event time limit is set #920

sunkup opened this issue Jul 18, 2024 · 2 comments
Labels
3rd party related to a third-party product (library, …) bug Something isn't working

Comments

@sunkup
Copy link
Member

sunkup commented Jul 18, 2024

Problem scope

  • I'm sure that this is a DAVx⁵ problem.

App version

  • I'm using the latest available DAVx⁵ version.

Steps to reproduce

  1. Setup account with caldav.gmx.net
  2. Set past event time limit to 400 days
  3. Create an event in the far future (ie. on 1.1.2026)

Actual result

The event is created but not shown in the local calendar.

Expected result

The event is created but and shows in the local calendar.

Further info

  • changing the amount of "past event time limit" days to a smaller number, ie 50, will trigger a re-sync and make the event show up again.
  • Exact number of "past event time limit" days and how far the event needs to be in the future, to not show up anymore, are still unknown.
  • May not be specific to GMX.

Originally posted by @pcjogi in #863

@sunkup sunkup added the bug Something isn't working label Jul 18, 2024
@devvv4ever
Copy link
Member

Please note that Synology has a similar problem with larger numbers for the past time event limit. Many servers do not support the FILTER method for higher values. And I remember that gmx is not delivering events to (at least CalDAV) clients if they are far in the future.

@rfc2822 rfc2822 added the 3rd party related to a third-party product (library, …) label Jul 21, 2024
@rfc2822
Copy link
Member

rfc2822 commented Jul 21, 2024

Yes, closing because as far as I know that's a GMX problem. Please re-open if it's related to DAVx5.

@rfc2822 rfc2822 closed this as not planned Won't fix, can't repro, duplicate, stale Jul 21, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in DAVx⁵ Releases Jul 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3rd party related to a third-party product (library, …) bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants