Parity apparatus efficiency: shard R cache, close automation loop, de…#136
Merged
Conversation
…dupe CI, pin dev env Cache sharding (schema v2): tests/_r_cache.json (15.7MB monolith, opaque hash keys) becomes tests/_r_cache/ with one JSON shard per R function label and keys of the form "<label>|<sha256>". Regeneration diffs now name the function they touch, git delta-compresses the shards, and a live-R run rewrites only the shard it changed. All 2314 entries were migrated by replaying tests/parity against the old monolith (the sha256 payload is unchanged, so legacy keys are the digest part of new keys); zero orphans, full suite green cache-only. regenerate_r_cache.py, run_live_r_parity_for_changed_api.py, the sync manifest/scripts, and docs follow the new layout. Automation loop: the regen workflow now records r_commit/r_version in sync/nns_source.json itself and posts a per-function changed-entry table in the PR body, so a cache PR is self-consistent and reviewable without forensic scripts. CI dedupe: native-backend-ci ran the identical Python 3.11-3.14 matrix twice per PR push (push + pull_request events). push is now main-only, with a concurrency group cancelling superseded runs. Dev env pinning: pre-commit hooks run ruff/mypy via `python -m` in the project environment, so local results match CI instead of a foreign mypy reporting spurious numpy import errors. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AxBV5HmXHY5nCUvW9SwDvb
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
2 participants
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.
…dupe CI, pin dev env
Cache sharding (schema v2): tests/_r_cache.json (15.7MB monolith, opaque hash keys) becomes tests/_r_cache/ with one JSON shard per R function label and keys of the form "|". Regeneration diffs now name the function they touch, git delta-compresses the shards, and a live-R run rewrites only the shard it changed. All 2314 entries were migrated by replaying tests/parity against the old monolith (the sha256 payload is unchanged, so legacy keys are the digest part of new keys); zero orphans, full suite green cache-only. regenerate_r_cache.py, run_live_r_parity_for_changed_api.py, the sync manifest/scripts, and docs follow the new layout.
Automation loop: the regen workflow now records r_commit/r_version in sync/nns_source.json itself and posts a per-function changed-entry table in the PR body, so a cache PR is self-consistent and reviewable without forensic scripts.
CI dedupe: native-backend-ci ran the identical Python 3.11-3.14 matrix twice per PR push (push + pull_request events). push is now main-only, with a concurrency group cancelling superseded runs.
Dev env pinning: pre-commit hooks run ruff/mypy via
python -min the project environment, so local results match CI instead of a foreign mypy reporting spurious numpy import errors.Claude-Session: https://claude.ai/code/session_01AxBV5HmXHY5nCUvW9SwDvb