#156 the iCal export of Budget calendar doesn't include all events
Opened 5 years ago by viorel. Modified 4 years ago

== Steps to replicate: ==

  1. Go to [[https://apps.fedoraproject.org/calendar/Budget/|Budget calendar]].

  2. Click on the [[https://apps.fedoraproject.org/calendar/ical/Budget/|iCal Export]] button (bottom right corner).

  3. Open the iCal file in a text editor.

== Actual result: ==

The last entry in iCal file is:

{{{
BEGIN:VEVENT
UID:20160306T174055Z-72204@fedocal01.phx2.fedoraproject.org
DTSTART:20160815T130000Z
DTEND:20160815T140000Z
DESCRIPTION: Fiscal Year: FY18\n Responsible: FCL\, Council\n\nMore
information available at:\nBudget.next
LOCATION:fedora-commops@irc.freenode.net
ORGANIZER:viorel
SUMMARY:Budget Session at Flock
END:VEVENT
END:VCALENDAR
}}}

== Expected result: ==

The iCal should include the events past the 2016-08-15 date. The events for 2016 can be viewed using the [[https://apps.fedoraproject.org/calendar/list/Budget/|list view]]. The last event is [[https://apps.fedoraproject.org/calendar/Budget/2017/7/17/|2017-07-17]].

The issue was briefly discussed on this [[https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/message/NJA7GUL5MJURDRHB2XYRI4JRWHG6SUOZ/|commops thread]].

Thanks!


Hi,

Thanks for your report.

So this is not a bug but the current/desired behavior. To reduce the load on the server, the iCal output only contains the last 30 days and the coming 3 months[1], but this is of course a sliding window, so in a month, you'll get in your iCal feed the meetings of the coming 3 months then.

In other words, you won't get the full list of meeting 6 months in advance but they will all get there eventually as you approach them.

Is this a problem for you?

[1] https://git.fedorahosted.org/cgit/fedocal.git/tree/fedocal/__init__.py#n622

Replying to [comment:1 pingou]:

So this is not a bug but the current/desired behavior.

Thanks, I'll change the ticket type to "enhancement".

To reduce the load on the server, the iCal output only contains the last 30 days and the coming 3 months[1], but this is of course a sliding window, so in a month, you'll get in your iCal feed the meetings of the coming 3 months then.
[...]
[1] https://git.fedorahosted.org/cgit/fedocal.git/tree/fedocal/__init__.py#n622

Given that the [[https://fedorahosted.org/fedocal/ticket/54|CalDAV support]] is still in works I couldn't think of any other way that would allow me adding the calendar to my desktop client so until that is resolved could restricting the full calendar download to users in "cla_done + 1" groups mitigate the abuse?

Alternatively since the API already allows the download of all events, all calendars, filters etc. -- if that's lighter on the server then I'd say there is no need to change the behavior, just informing users about the date range before or after the download to avoid the confusion?

Given that the CalDAV support is still in works I couldn't think of any other way that would allow me adding the calendar to my desktop client so until that is resolved

That is true, iCal is currently the only way to sync a calendar with a desktop/phone calendar.

could restricting the full calendar download to users in "cla_done + 1" groups mitigate the abuse?

This won't work since iCal does not require authentication, so when to request the iCal feed from wget or from your desktop app, we do not know who you are :)

Replying to [comment:3 pingou]:

That is true, iCal is currently the only way to sync a calendar with a desktop/phone calendar.

could restricting the full calendar download to users in "cla_done + 1" groups mitigate the abuse?

This won't work since iCal does not require authentication, so when to request the iCal feed from wget or from your desktop app, we do not know who you are :)

It doesn't for iCal but to add events/calendars FAS is required 1 however, if your answer to the question "Is there an easy fix to restrict the full calendar download to FAS authenticated users?" would be "No." then we can close this ticket and move on to the next one ;)

Login to comment on this ticket.

Metadata