Repository navigation
fix: preserve snapshot metadata and recover deeply nested values - #60
Merged
Merged
Conversation
3 tasks done
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.
Small application string budgets currently truncate frame identifiers and attribute names, and an excessively deep value can discard the other variables in its frame. Give diagnostic text and bytecode separate bounded budgets, preserve namespace and attribute names, and recover recursion failures at root mapping entries so unrelated locals remain available. Keep relative source paths usable when the working directory has been removed.
Document these bounds and add regressions for tiny string budgets, namespace aliasing and priority, deep lists/mappings, deleted working directories, and metadata limits in normal and unlimited captures.
Refs #58. Second PR in the series. PR #59 is merged, and this PR now targets
main; the diff contains only metadata and recovery changes.Validation on CPython 3.13.15:
git diff --check, and strict Sphinx build passed.CI on the latest head: all 10 checks passed, covering Linux Python 3.11–3.15, Windows/macOS Python 3.14, quality, documentation, and distributions. Workflow run.