I have to say my impression was that your codebase looks quite well structured, so don't be too hard on yourself.

It's also quite tricky to parse various badly defined flavors. There will always be ugly special cases.

I can confirm that it works with the 0.8.0 from flatpak.

Oh I see. I didn't think about fixing it in that way.

What would your preferred fix then look like ?

Ok, can confirm:

• https://fahrplan.events.ccc.de/congress/2024/fahrplan/schedule/export/schedule.xml has "2024-12-27" as start
• https://api.events.ccc.de/congress/2024/schedule.xml has "2024-12-27T09:30:00+00:00" as start

Frab defines this as xs:date: https://github.com/frab/schedule.xml/blob/master/schema/schedule.xml.xsd#L20C1-L20C73

But their own schema make it more complicated: https://raw.githubusercontent.com/voc/schedule/master/validator/xsd/schedule.xml.xsd

Would you be open to accepting their format if I send over a patch? I could normalize it when reading the file initially.

This seems to be stored as the "start" value in the meta table of the event.

Hi,

Was trying to open the "38C3 - merged" event info and it fails with "time data '2024-12-27T09:30:00+00:00" does not match format '%Y-%m-%d %H:%M:%S'".

Some interesting observations:

• "38C3 - main rooms only" does not fail with the same error
• it only does this on the second opening of this event info. On the first opening of this event info it works without error.

Trying to understand what's going on.