Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: raise proper error instead of panicking when result of truncation is non-existent datetime #14958

Merged
merged 1 commit into from
Mar 10, 2024
Merged

fix: raise proper error instead of panicking when result of truncation is non-existent datetime #14958

merged 1 commit into from
Mar 10, 2024

Commits on Mar 10, 2024

  1. fix: raise proper error instead of panicking when result of truncatio… 

    …n is non-existent datetime
    @MarcoGorelli
    MarcoGorelli committed Mar 10, 2024
    Configuration menu
    Copy the full SHA
    ca2d1ad View commit details
    Browse the repository at this point in the history