Fix stale SDK index blocking scheduled updates - #1389
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 Flutter engine update in e7ba211 added a mapping after the v5 index snapshot was generated. The merged index therefore contained 583 engines while its source contained 584. The scheduled updater ran the stale-index test before reaching its index-generation step, preventing recovery.
Regenerate the missing index entry and refresh indexes from checked-out provider data before the scheduled tooling tests. PR validation still rejects stale indexes; the final update/check sequence remains unchanged. Add a regression covering stale detection after a provider adds data, rebuilding, and deterministic repeated generation.
Validation: SDK tooling 18 tests, offline SDK update check (584 engines / 684 releases), canonical check (2832 rules), rules suite 8 tests, chart suite 17 tests, and diff check. No SDK fetching, release publication, or changes to the frozen English-label bootstrap commit are included.