release: v3.2.4 — cap ALL flat viz sections (final page-size pass) - #110
Merged
Conversation
After v3.2.3 the deployed self-analysis.html was still ~4.9 MB: capping program points alone wasn't enough — Diagnostics (~1.7 MB), Call graph (~1.7 MB), Trap checks, Functions, gaps/handle/float/pentagon each render one row per entry, and scry-on-scry produces thousands of each. scry-viz: a shared SECTION_ROW_CAP (100) + cap_note applied to every flat section; the call-graph Mermaid diagram is skipped for graphs > cap (a thousands-edge Mermaid source was itself ~1.7 MB). Trap checks show POTENTIAL-TRAP first so the cap never hides one. New comprehensive test blows up EVERY section to 4000 entries and asserts the page stays <1 MB (would have caught the earlier partial fixes). Full un-capped data remains in guidance.json. Version 3.2.3 → 3.2.4 + Cargo.lock. 25 viz tests, clippy + fmt clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Post-deploy verification of v3.2.3 showed
self-analysis.htmlstill ~4.9 MB — the points cap worked, but Diagnostics (~1.7 MB), Call graph (~1.7 MB), Trap checks, Functions, and the fact sections were uncapped.Fix
SECTION_ROW_CAP(100) + "showing N of M" note: Diagnostics, Call graph, Trap checks (POTENTIAL-TRAPs first), Functions, gaps, handle/float/pentagon facts.all_flat_sections_capped_page_stays_small: blows up every section to 4,000 entries, asserts page <1 MB. This is the guard that would have caught v3.2.2/v3.2.3.Full un-capped data stays in
guidance.json. Bump 3.2.3 → 3.2.4. 25 viz tests, clippy + fmt clean.rivet validatePASS.🤖 Generated with Claude Code