-
Notifications
You must be signed in to change notification settings - Fork 13
fix(signage): keep display updates, cron and metrics reliable #526
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
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If a cron takeover has a
play_periodlonger than 366 days, the new search cap can hide its start while the run is still active. For example, a February 29 run with a 368-day period is still active on March 2, 2025, but the player cannot find it and stops showing it. The search needs to cover the configured period.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 209e804. The search limit is now the requested period, capped at 10 years. To keep long searches cheap, both searches skip local days the cron cannot match (one check per day), and crons that can never run at any time of day return at once. Measured: a 10-year search for
0 0 31 2 *takes about 5 ms. Test: "finds a run that started more than a year ago" (0 0 29 2 *, 368-day period, checked on 2 Mar 2025).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The remaining case is a deliberate limit, not an oversight. The search now covers the requested period, with a 10-year ceiling. Without a ceiling, a corrupt or extreme
play_period(the manager sets no maximum) would make each schedule tick walk an unbounded number of days on low-power display hardware. A run is now missed only if its period exceeds 10 years and it started more than 10 years ago. For signage, a takeover that long is effectively permanent, and a background schedule is the right tool for it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That addresses the concern. Using the requested play period preserves long-running takeovers, while the 10-year ceiling is a reasonable defensive bound against an unbounded walk on display hardware. Given the stated behavior for periods beyond the ceiling and the fallback to background schedules for effectively permanent content, I’m withdrawing this finding.