#212 "Unparseable" entry in schedule for Fedora 45
Closed by amoloney. Opened by ksurma.

The calendar available to download from https://fedorapeople.org/groups/schedule/f-45/f-45-key-tasks.html contains an "#UNPARSEABLE" first entry which impacts the UIDs of the rest of the calendar events. I suspect the "#UNPARSEABLE" was in fact supposed to be Fedora Linux 45 release, similar to other calendars:

BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//python-schedules-tools//ICS handler//
SUMMARY:Fedora 45 Schedule
UID:Fedora_45_Schedule
BEGIN:VEVENT
SUMMARY:#UNPARSEABLE
DTSTART:20250213T080000Z
DTEND:20271201T165959Z
DTSTAMP:20250730T093721Z
UID:1-_unparseable
DESCRIPTION:
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
SUMMARY:Key Tasks & Milestones
DTSTART:20250213T080000Z
DTEND:20271201T165959Z
DTSTAMP:20250730T093721Z
UID:22-_unparseable.key_tasks_milestones

That is exactly what its meant to be, and the formula that was in the smartsheet (where the schedule originates from) kept coming in #unparsable, so i thought I removed the formula altogether in favour of a manual entry....but clearly that either didnt work or I didnt do it.

Thanks for reporting, I will take a look today/tomorrow and see can I fix the error and generate a new schedule.

Metadata Update from @amoloney:
- Issue assigned to amoloney

@amoloney there's a decent chance that this is due to me getting cute with how we handle release numbers in Smartsheet (to avoid the inevitable "oh crap, I forgot to update this one entry"). Happy to help you diagnose this if you need it.

It'll either be you or chatgpt that will solve it....but I favour your odds to help me more so yes, yes please :pray:

Hi @ksurma I think Ben and I found the root of the problem. Ive re-uploaded a new schedule, can you confirm that the issue is now resolved and let me know please? Thanks!

closing as I think this is resolved now

Metadata Update from @amoloney:
- Issue status updated to: Closed (was: Open)

Metadata