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.

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

Ensure datetimes are timezone aware when comparing in max() #33

Closed
wants to merge 3 commits into from

Conversation

brylie
Copy link

@brylie brylie commented Sep 18, 2020

Description of change

Absence of BOOKMARK_KEY was causing errors with date comparison. This PR adds a check for BOOKMARK_KEY and logs info about the result for debugging purposes.

Closes #31

@cmerrick
Copy link

Hi @brylie, thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes.

@cmerrick
Copy link

You did it @brylie!

Thank you for signing the Singer Contribution License Agreement.

@brylie brylie changed the title Bookmark key handling Ensure datetimes are timezone aware when comparing in max() Sep 18, 2020
@karanpanchal-crest karanpanchal-crest requested review from KAllan357 and removed request for KAllan357 June 3, 2021 06:01
@brylie brylie closed this Jul 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CRITICAL can't compare offset-naive and offset-aware datetimes
2 participants