Skip to content

Conversation

sorgo
Copy link

@sorgo sorgo commented Apr 25, 2023

I experienced multiple times a glitch in ntp sync that resulted in setting the date to year 2080. This is a quick dirty fix to mitigate the issue and let the system run the sync again

I experienced multiple times a glitch in ntp sync that resulted in setting the date to year 2080. This is a quick dirty fix to mitigate the issue and let the system run the sync again
@sorgo sorgo changed the title Update __init__.py Do not accept wrong dates (e.g. 2080) Apr 25, 2023
Copy link

@oddstr13 oddstr13 left a comment

Choose a reason for hiding this comment

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

It would be better to figure out why you are getting an unexpected date from ntp than hardcoding it here now.

In 26 years, it will be a problem for everyone if this is merged.

Hardcoding a lower limit is OK, as we are querying for the current datetime, and 2020 should hopefully never happen again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants