docs(ci): the sweep converges in hours, not 15 minutes - #157
Merged
Merged
Conversation
GitHub does not honour '*/15' in this org. Measured across 12 consecutive scheduled runs of homelab-stacks eir-windmill-sync (same cron, same org), the real interval was 98 to 287 minutes, median 135. The sweep is still a real backstop and the event path still handles the normal case immediately, but the comments claimed a 15-minute convergence that does not hold. Corrects them so nobody sizes a timeout or an alert against it.
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.
Correcting a claim I made in #151/#153 that turns out not to hold.
GitHub does not honour
*/15in this org. Measured across 12 consecutive scheduled runs of homelab-stackseir-windmill-sync(same cron, same org): 98 to 287 minutes apart, median 135.So the sweep converges in hours, not minutes. It is still a real backstop (the previous behaviour was never converging) and the event path still handles the normal case immediately, but the comments claimed a 15-minute guarantee that is false, and someone could reasonably size a timeout or an alert against it.
The same measurement forced a threshold fix in the pin-drift alert: Emkraan/homelab-stacks#451.
No behaviour change here, comments only.