record api_last_activity as timezone aware timestamp #52
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…with notebook status api when producing last_activity timestamp)
Member
|
Thanks! I'll merge this now and if there is a problem we can follow up in a new PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
fixes problems with notebook status api when producing last_activity timestamp.
i.e. in this line https://github.com/jupyter/notebook/blob/4f9a6cbdd81ed26a7979d993766d7223e1c72e5c/notebook/notebookapp.py#L367
when comparing (max(...)) all timestamps it produces a
TypeError: can't compare offset-naive and offset-aware datetimes