[LFXV2-882] Fix date parsing to log warnings instead of returning errors

[andrest50]

Summary

• Changed date parsing error handling to log warnings instead of returning errors
• Prevents valid participant data from being dropped due to malformed date strings
• Added additional context to warning logs for better debugging
• Bumped chart version to 0.3.6

Ticket

LFXV2-882

Changes

• handlers_meetings.go:
  • Modified convertInviteeToV2Participant to log warnings for CreatedAt/ModifiedAt parsing errors
  • Modified convertAttendeeToV2Participant to log warnings for CreatedAt/ModifiedAt/JoinTime/LeaveTime parsing errors
  • Added invitee_id, attendee_id, and meeting_and_occurrence_id to warning logs
  • Only set date fields when parsing succeeds
• Chart.yaml: Bumped version from 0.3.5 to 0.3.6

Behavior Change

Previously, when date fields couldn't be parsed as RFC3339, the entire participant record would fail to sync with an error. Now, the system logs a warning and continues processing, allowing the participant data to be indexed without the problematic date fields.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR addresses a critical data synchronization issue where malformed date strings in Zoom meeting participant data would cause entire participant records to be dropped. By changing date parsing failures from errors to warnings, the system now logs the issue and continues processing, allowing participant data to be indexed without problematic date fields.

Key Changes:

• Modified error handling in date parsing from returning errors to logging warnings
• Added contextual identifiers (invitee_id, attendee_id, meeting_and_occurrence_id) to warning logs for better debugging
• Bumped Helm chart version to reflect the bug fix

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
cmd/lfx-v1-sync-helper/handlers_meetings.go	Updated convertInviteeToV2Participant and convertAttendeeToV2Participant to log warnings for date parsing failures instead of returning errors, allowing partial data to be processed
charts/lfx-v1-sync-helper/Chart.yaml	Bumped chart version from 0.3.5 to 0.3.6 to reflect the bug fix

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[mauriciozanettisalomao]

Just a minor comment: an idea to try loading v1 data into v2 as much as possible.

[mauriciozanettisalomao]

Not related to the change you made, but I'm assuming our source data is kinda inconsistent with the dates, so maybe we could try different date formats to actually get the data into v2 as much as possible.

Here's an example (not elegant at first glance, I know, but it works when the source doesn't follow a pattern):

• https://github.com/linuxfoundation/lfx-pet-cventwebhook/blob/main/helper/common.go#L70-L119

Maybe this could be a backlog ticket.

[emsearcy]

that's a good idea, though in this case somehow that field actually got the value left the meeting. Reason : left the meeting (the leave reason being stored as the leave time, not sure if it's itx-zoom's fault or bad data in the Zoom webhook itself.

Also I believe Meltano is actually be doing some date normalization already. I just checked the autodetected/built Dynamo ingest scheme, and these are getting considered as datetime fields—and while we turned off schema validation for Dynamo-replicated data, because it was so inconsistent—meaning individual fields are coming across with different schemas, so some records will be a "string" instead of a "datetime"—the ones that do get parsed as a datetime are, I believe, converted to python datetime.datetime in transit, and then back to JSON.