[vrms.io] Most meeting times are stuck at "2024-03-xx" - "2024-04-xx"

[fyliu]

Dependency

• [ ] Close if the following issue is completed: https://github.com/hackforla/VRMS/issues/1872

Overview

Most meetings look to be incorrectly stuck at "2024-03-04"-"2024-03-11", and some "2024-04-xx". Peopledepot was one of them and got unstuck by updating the event.

Action Items

I'm not sure if there's a way to reproduce and test fix this in dev/staging. These instructions are targeting production

• [ ] confirm the problem
• [ ] apply some solution
• [ ] verify the problem is solved (go to the recurringevents output and search for the affected dates, or make sure the code is not generating any events belonging in the distant past.)

Resources/Instructions

• This issue is part of the epic: https://github.com/hackforla/VRMS/issues/1838

Slack conversation about the issue From #people-depot slack message:

Fang: Interesting... The VRMS site wasn't listing our meetings before and I manually toggled the "ready" switch before our meetings for a while and then stopped some time ago. I thought it was because their team was in some transition phase where they'll fix all the events once they're done, but it didn't happen and I forgot to follow up.

Anyway, I remembered today and checked their daily events output for our project (peopledepot), and saw that our meeting date and time was set to something like "2024-03-08", see this commit for that data.

So I thought: if I went and updated that meeting, maybe it'll get processed with their current backend event logic. I updated our zoom link for the event and now our next meeting time is "2024-10-18T00...", which I assume is UTC for the correct time. So we can try going to VRMS.io at the next meeting to see if we're listed.

Furthermore, there seems to be 7 other projects that are stuck at the "2024-03-08" meeting date. Maybe their members also aren't logging their volunteer hours?

There's some commits around 2024-03-08 dealing with generating recurring events that might have done this.

• Looks like the affected events range from 3/4-3/11, which corresponds to the commit dates. Most meetings are affected. Like the search results for "03-" covered >70% of the events on the page.

• looks like the only events not affected are the Expunge Assist PM, the 3 Research/UX-UI meetings, and PeopleDepot at this point.

• There's some meetings at 2024-04-xx as well, like a DevOps meeting.