Repository navigation
[codex] add snapshot import cache metadata - #71
Merged
Merged
Conversation
9 tasks
codeasier
commented
Jul 28, 2026
codeasier
left a comment
Owner
Author
There was a problem hiding this comment.
Two correctness issues found in metadata validation.
codeasier
commented
Jul 28, 2026
codeasier
commented
Jul 28, 2026
codeasier
marked this pull request as ready for review
July 28, 2026 06:08
codeasier
force-pushed
the
codex/snapshot-import-cache-metadata
branch
from
July 28, 2026 06:12
f7a7037 to
ae44b0e
Compare
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 changed
pt_snap_metadatatable and preserve atomic database replacementpt-snap metadata,--force, Python API metadata access, and an MCP metadata toolWhy
Large PyTorch snapshot pickles can take significant time and resources to replay. Repeated imports previously rebuilt the same database with no reliable compatibility check or provenance information.
Impact
Identical imports now reuse the existing database. Legacy or incompatible databases rebuild once, users can force a rebuild, and CLI/API/MCP callers can inspect normalized metadata. MCP import remains out of scope.
Validation
pytest -q(354 passed)ruff check src tests --no-cacheblack --check src testspython -m basedpyright(0 errors, 0 warnings)Closes #77