Fixing sleep time to wait for exact next second.#429
Open
fx-kirin wants to merge 2 commits intoahawker:masterfrom
Open
Fixing sleep time to wait for exact next second.#429fx-kirin wants to merge 2 commits intoahawker:masterfrom
fx-kirin wants to merge 2 commits intoahawker:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Crython depends on accuracy of
time.sleep(1)oftab.py.It can cause delays, and the delays accumulate. So sometimes a second can be ignored because of it, like sleep starts at 13:01:21.99 and wakes up at 13:01:23.01. This case, the cron job matched to 13:01:22 will not be executed.
This fix will repair the ignorance.