eschutho opened a new pull request, #40127: URL: https://github.com/apache/superset/pull/40127
## Summary - `result_set.py`: `pd.to_datetime(series, utc=True)` defaults to `errors='raise'`. Dates beyond ~2262-04-11 overflow pandas' int64 nanosecond representation and raise `OutOfBoundsDatetime`. The surrounding `except Exception` catches it but logs at ERROR level via `logger.exception()`, causing the error to surface repeatedly in observability tooling for any auto-refreshing chart that queries the affected table. - `commands/dataset/importers/v1/utils.py`: same missing `errors="coerce"` on the CSV import path — belt-and-suspenders fix. Note: silent coercion during import could mask a data-quality issue (e.g. a file with bogus timestamps imports silently with NaT instead of failing visibly). `NaT` is preferable to clamping (clamping silently lies — year 3118 would show as 2262 in charts) and to converting to string (breaks the PyArrow column schema). ## Test plan - [ ] Query a dataset containing a timezone-aware datetime column with a value beyond 2262 (e.g. `3118-01-01`) — chart should render with a null cell instead of logging an error - [ ] Import a CSV with an out-of-range datetime column — import should succeed with NaT for the out-of-range values - [ ] Confirm no regressions on normal datetime columns within the representable range 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
