Repository navigation
fix: simplify native TOML config reading and restore error columns - #1085
Merged
Merged
Conversation
kvlonge
enabled auto-merge (squash)
October 12, 2026 01:15
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.
Why
The native TOML config reader carried about 700 lines of shims reproducing Python
tomllibedge cases, and its errors had lost column locations and mentionedtomllib. This PR also carries the 0.156.0 release memory exception for the 3,000-modellineageguards, which missed #1086: the accepted lineage memory growth puts them at 130–137 MiB against a 128 MiB cap.Changes
tomllibaccepts still load identically; failure baselines updated.Verification
make check-cipass;fensu checkpasses after the test-case fix.