Tune cycle freshness for nightly source dreams#2505
Open
sene1337 wants to merge 2 commits into
Open
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
2 participants
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.
Summary
This PR makes
doctor.cycle_freshnessmatch an intentionally once-nightly dream cadence:doctor.cycle_freshness.source_allowlist/source_ignorelist, withDREAM_SOURCE_ALLOWLISTas a runtime fallbackdoctor.cycle_freshness.warn_hoursanddoctor.cycle_freshness.fail_hoursgbrain config set ...works without--forceWhy
A once-nightly dream cron cannot stay green under the old 6h warn / 24h fail defaults, even when it is healthy. Operators can now set daily-with-grace thresholds once in DB config, e.g. warn at 30h and fail at 48h, and have both interactive and HTTP/remote doctor use the same cadence.
Verification
bun test test/doctor-cycle-freshness.test.ts test/config-set.test.tsbun run typecheck