Add initial "hole-filling" experiment - #147
Draft
tianon wants to merge 4 commits into
Draft
Conversation
tianon
marked this pull request as draft
August 21, 2026 20:14
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.
This is a script to calculate our "holes" based on Git history -- it's not fast, but it is efficient, and it's maybe "fast enough" with a reasonable
HOLES_SINCEupper-bound set. I need to spend more time reviewing/thinking about it. Avoiding Docker Hub lookups for our "holes" calculation is very attractive, since it means we could commit the resultingholes.jsonand have the full source-of-truth for any arbitrary suppportedlibrary/xxxtag fully sourced deterministically from meta.