Bug Scrub every other wednesday morning - calendar issue

[kingdonb]

Something is wrong with the time zone calculation or something like that, in the Flux Community calendar.

It's supposed to drop items from the calendar once they are at least 50 minutes in-progress - this works in a way, because when we have a Flux Dev Meeting on Wednesday and a Flux Bug Scrub on Thursday, the Dev Meeting successfully falls off the calendar in time to put the Flux Bug Scrub on the main page in time before it's happening.

However, when Flux Bug Scrub is happening first thing Wednesday morning (8am Eastern time) and the website refresh runs, either 2am Eastern Time or 8:00am Eastern time, by the time that Flux Bug Scrub is starting Wednesday morning, it has already fallen off the calendar - so it's very difficult for people who haven't subscribed their Google Calendars via the .ics to find the entry into this meeting.

I try to keep Bug Scrub low key, advertising to a minimum to keep the quality of visitors high, but that's too low-key - it should absolutely be possible to show up 10 minutes late for Bug Scrub and still find the entry link on the front page of the website.

[kingdonb]

I've seen this issue for at least a year, but debugging it requires either time-traveling (a debugging technique, not literal time travel) or waking up very early on a Wednesday morning to attempt to see the issue reproducing itself in real-time.

I'm assuming that there is somewhere that time is being reported or interpreted in a local time zone in the GitHub Actions runner, when it's actually a UTC time that is being passed, or the inverse of that.

The bit of code that drops events when they are 50 minutes old is here:
https://github.com/fluxcd/website/blob/f198d60df470f33d037b059763c35e4bd9f45fd8/hack/import-calendar.py#L82

Will try to get it solved before two weeks from now Wednesday morning. There isn't really any impact on the Dev Meeting attendance because we do have a persistent agenda document there, and the Zoom meeting link is posted prominently at the top of that agenda doc.

Maybe I can solve it without time-traveling by using an LLM (or even a static type-checker?)