Fix: Ensure consistent datetime handling during CSV import #3244
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses a bug where the CSV importer would fail with a
TypeError
when encountering certain datetime formats with timezone offsets, even if those formats were individually parseable bydateutil
. The error stemmed from Pandas' inconsistent timezone inference across chunks of the DataFrame.The fix adds
utc=True
to thepandas.to_datetime
call within theread_and_validate_csv
function intimesketch/lib/utils.py
. This forces all parsed datetimes to be explicitly represented in UTC, preventing timezone-related parsing errors and ensuring consistent datetime handling.Key Benefits:
TypeError
during CSV import for a broader range of datetime formats.This change is backward compatible and should not affect existing timelines or functionality.