Skip to content

fix: int is too small for a unix timestamp #2079

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

Merged
merged 2 commits into from
Jan 9, 2023
Merged

Conversation

allisonsuarez
Copy link
Contributor

@allisonsuarez allisonsuarez commented Jan 9, 2023

Changed dashboard summary model in comment to use last_successful_run_timestamp: Optional[float] = None since a value like 1668725028.424 is too large to be casted to an int

Signed-off-by: Allison Suarez Miranda <[email protected]>
@boring-cyborg boring-cyborg bot added area:common From common folder category:models labels Jan 9, 2023
@Golodhros Golodhros added type:bug An unexpected problem or unintended behavior status:completed Issue is completed and on master labels Jan 9, 2023
Copy link
Member

@Golodhros Golodhros left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Signed-off-by: Allison Suarez Miranda <[email protected]>
@allisonsuarez allisonsuarez merged commit a2cb0b2 into main Jan 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:common From common folder status:completed Issue is completed and on master type:bug An unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants