You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Timestamps are disabled by default for CSV because of the option to have time zone info in the time stamp which cudf does not support. If we enable them they only work for dates after 1902 and before the end of 2038. These look like overflow/underflow issues.
If you try to parse a timestamp column in CSV as a date it is even worse. It looks like it tries to read in the time information and parse it for days and just ends up producing really large numbers.
Steps/Code to reproduce bug
New tests are being pushed to the integration tests that reproduce this.
The text was updated successfully, but these errors were encountered:
Describe the bug
Timestamps are disabled by default for CSV because of the option to have time zone info in the time stamp which cudf does not support. If we enable them they only work for dates after 1902 and before the end of 2038. These look like overflow/underflow issues.
If you try to parse a timestamp column in CSV as a date it is even worse. It looks like it tries to read in the time information and parse it for days and just ends up producing really large numbers.
Steps/Code to reproduce bug
New tests are being pushed to the integration tests that reproduce this.
The text was updated successfully, but these errors were encountered: