Repository navigation
chore: bump TechEngine submodule to dc6d07e - #384
Merged
Merged
Conversation
This brings in two TechEngine PRs: - GetTechAPI/TechEngine#129: Tier 1 no longer calls a page dead just because HEAD failed. A HEAD error other than 429/503 now falls back to GET, and GET's answer decides. Kaggle dataset pages answer HEAD with 404 and GET with 200, so every record citing one counted as having a dead source, including 145 of the tablets in the last release. - GetTechAPI/TechEngine#128: TechEngine's own final check. TechAPI doesn't run it. collect.yml's three `uses:` move to the same commit. The reusable workflows are unchanged since 3c50cb8, and the validator and the dump code didn't change either. Refs #297
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
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.
What
Moves the TechEngine pin from
3c50cb8todc6d07e, and movescollect.yml's threeuses:to the same commit.The new pin brings in two TechEngine PRs:
kaggle.com/datasets/msainani/gsmarena-mobile-devices.Why now
collect.yml'spromoteandfinal-check.yml's verification both run this engine. Without the fix, promotion holds back records whose only source is a Kaggle dataset.Checks
3c50cb8is an ancestor ofdc6d07e. The only commits between them are feat(data/cpu): weekly ingest #128 and data(verify): verified promotions (2026-07-27) #129.ingest.yml,refresh.ymlandverify-promote.ymlare unchanged.app/validate.pyand the dump code are untouched. pr-checks runs the full engine validator and a smoke dump, because the pin moves.Closes #297