Summary of Changes

Hello @A1K28, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

I've addressed a ValueError that was affecting XVR tests, specifically related to the parsing of timestamp strings. The core of the problem was datetime.fromisoformat failing when timestamps had fractional seconds with fewer than the expected six digits. My changes introduce a robust method to normalize these timestamp strings by padding the fractional seconds with zeros, ensuring they are always in a format that datetime.fromisoformat can successfully process. This makes the example pipeline more resilient to variations in timestamp data precision.

Highlights

• Timestamp Parsing Fix: I've implemented a fix for ValueError that occurs when datetime.fromisoformat attempts to parse timestamp strings with fractional seconds that are not exactly six digits long. This is a common issue when dealing with varying precision in timestamp data.
• Robust Timestamp Normalization: The solution involves using a regular expression to detect and pad the fractional second part of the timestamp string with trailing zeros, ensuring it always has six digits (microseconds) before being passed to datetime.fromisoformat. This makes the parsing robust to different input precisions.
• Broad Application in Example Pipeline: This fix has been applied to both the main timestamp field and all derived pickup_datetime fields (year, month, day, weekday, hour) within the streaming_taxifare_prediction.yaml example, ensuring consistent and error-free date-time extraction.