Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
3 tasks
fyliu opened this issue Oct 15, 2024 · 0 comments
Open
3 tasks

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

fyliu opened this issue Oct 15, 2024 · 0 comments
Labels
Bug p-feature: Events Research Researching best approach/solutions role: Dev Lead role: devops size: 3pt Can be done in 13-18 hours

Comments

@fyliu
Copy link
Member

fyliu commented Oct 15, 2024

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

  • 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.

@github-project-automation github-project-automation bot moved this to New Issue Approval in P: VRMS: Project Board Oct 15, 2024
@fyliu fyliu changed the title [vrms.io] Some meeting times are stuck at "2024-03-xx" - "2024-04-xx" [vrms.io] Most meeting times are stuck at "2024-03-xx" - "2024-04-xx" Oct 15, 2024
@JackHaeg JackHaeg added this to the 04.03 User Feedback milestone Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug p-feature: Events Research Researching best approach/solutions role: Dev Lead role: devops size: 3pt Can be done in 13-18 hours
Projects
Status: New Issue Approval
Development

No branches or pull requests

2 participants