Repository navigation
Start GEFS 35-day virtual updates before extension completion - #1175
Merged
Merged
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.
The GEFS 35-day virtual update currently starts at 03:45 UTC, after the full extension was already available on 26 of 29 surveyed days. Start it at 02:15 UTC so the pod is polling before the previous cycle's final overnight dump, and extend its deadline to 8h30m to retain coverage of the new cycle's short leads and morning extension members.
Polling ends at 10:38 UTC with the existing seven-minute validation grace, covering the measured morning wave through 10:06 UTC. The init-relative
CheckCurrentDataallowance remains 3h50m; validation monitoring derives its timing from the new deadline, and the next-fire check still allows the validation retry. Update the arrival-pattern comment, timing tests, and documentation of latency during inactive gaps. Correct the recovery comment to describe one missed daily fire; the 72-hour update window is unchanged.Validation: 210 affected dataset/shared tests passed, including the source-backed integration and freshness-deadline checks; Ruff format/check and ty passed. The change targets prompt full-set completion; it does not guarantee sub-minute visibility for every individual file.