Use bundle-certified dataset materialization - #503
Draft
anth-volk wants to merge 18 commits into
Draft
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
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.
Fixes #502
Summary
materialize_datasetdispatcher that returns the selected source URI, local file path, logical name, and optional bundle provenance_use_bundle_dataset,_download_hugging_face_dataset, and_use_local_dataset; none of the private outcome functions uses “materialize” in its namepolicyengine-*-dataand Populace artifacts without package-name dispatchallow_unmanaged=TrueVerification
uv run make lint: passeduv run make test: 803 passed with 86% statement coveragematerialize_datasetimport check: passeduv lock --check, dependency compatibility, and bundle metadata checks: passedThe full test suite used local and mocked data only; live private-dataset integration was not run because this environment does not have an authorized Hugging Face token. The repository-wide mypy command is not currently a passing local project check: its configuration specifies unsupported Python 3.9 and it reports existing errors across unrelated modules.