Repository navigation
Rebind central-factor-packed pins so community-batch952 admits current sources - #2
Open
unpaidmoon wants to merge 1 commit into
Open
unpaidmoon wants to merge 1 commit into
unpaidmoon wants to merge 1 commit into
Conversation
…rces The historical packed audit still pinned five files from before the CrocSwap#2194 and related tooling merges, so admit_sources() rejected current main and failed the shared r439 workflow. Refresh those pins and record that the replay receipt matches the current certificate, whose only change from the original digest is three embedded source hashes. Co-authored-by: unpaidmoon <unpaidmoon@users.noreply.github.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.
Change and mathematical scope
Tooling pin refresh. No new κ, no supplier, no selected-frontier change. Selected κ stays
0.001672660197076918.research/central-factor-packed/verify.pyrefused current main before any coefficient check.admit_sources()still pinned five files from before the CrocSwap#2194 production wiring and the related CrocSwap#2001/CrocSwap#2054 tooling merges..github/workflows/community-batch952.ymlruns that verifier in the samefinitejob as everyresearch/r439-*pull request, so the stale pins turned the job red even when the PR's own replay passed.Five live pins in
SOURCES.jsonnow match canonical mainbb4bccbf42844d2801487450727c2f63e10d1d0f. The other 38 pins and the package base47481c89fd30a43f8f882eb4b391e89c29273fd0are unchanged. The complete packed replay then matchescertificates/dyadic-central-factor.jsonbyte for byte (receipt_sha2562aabc7e3ed38a27902f88244b80bed579e8ec2158c6ad3253f1c654c79b299e0,coefficients_checked6760000). That certificate differs from the package's original receiptffae0f0a22863718e3134a924592dcf4b05e919223323ba536c587c592bfe6a1only in three embeddedsource_sha256entries:scripts/exclusion_circuit.pyscripts/experiments/complex_centers.pyscripts/experiments/disjoint_tensor.pyscripts/shared_point_circuit.pyalso had to be re-pinned; it is not a certificate source.VALIDATION.jsonandBENCHMARK.jsonstay the October 13 record againstffae0f0a.Task and overlap
bb4bccbf42844d2801487450727c2f63e10d1d0f(canonicalCrocSwap/integer-mult-boundsmain; priority revision 6).central-factor-packedpins. The random task picker was not used.-mpopcnt, the replay-runtime lever already taken) andresearch/central-factor-production/(the Tooling: 44× faster production verify_factor via packed-row equality with identical receipts CrocSwap/integer-mult-bounds#2194 wiring this refresh admits, not a second algorithm).central-factor-packed,community-batch952, ordyadic-central-factor.Ordered eligible list used for this session (session 3 of 3), after dropping claimed, delivered, and open-PR work, and after dropping the flag-9 head-step repair in CrocSwap#4107:
uniform-transfer-audit). Left for another session.community-batch952central-factor pins — Handoffs and requests for independent checks CrocSwap/integer-mult-bounds#1166 comment 19046528.Priority-table next decisions were ineligible before that list: CrocSwap#3259 review delivered; flag-9 head-step is CrocSwap#4107; joint-query producer work is in open PRs including CrocSwap#3181; selected-stock binding is open CrocSwap#3898; the V45 ledger audit is open CrocSwap#3911; the scatter mutant is open CrocSwap#3801; the
01021323/ L22 prune work is in open PRs including CrocSwap#3821 and CrocSwap#3708.Validation
CPython 3.12.3, repository root:
verify.py:PASS_CENTRAL_FACTOR_PACKED, scopecomplete_historical_audit,coefficients_checked6760000,receipt_sha2562aabc7e3…, 1.901 s.test_packed.py: 11 tests OK in 3.656 s, including 1,344 scatter replacements and 231 gather sign flips and deletions.python3 -O -B test_packed.py: 11 tests OK in 3.630 s.Not run: hosted
community-batch952, fullmake verify, the selected cold replay, Lean, Docker. The certificate comparison is a byte match of the regenerated historical audit, not a new proof of the central factor.Credit
Nick Petalas for the CI finding. Ross Richardson for the packed adapter. Wentao Li for the CrocSwap#2194 / CrocSwap#2001 / CrocSwap#2054 production tooling whose bytes these pins now admit. Douglas Colkitt for the dyadic central factor. Prepared by unpaidmoon with substantial Cursor Grok assistance. Apache-2.0. No independent human or formal-kernel review is claimed.
Open next questions
community-batch952.ymlkeep running the historical packed adapter on everyresearch/r439-*change, or should that job callresearch/central-factor-production/verify.pyand leave the historical pins frozen at47481c89? This PR chooses the pin refresh the finding named, so the existing job can pass.scripts/shared_point_circuit.pyis admitted bySOURCES.jsonbut is not in the certificate'ssource_sha256map. A later edit of that file will again fail the r439 job without changing the central-factor receipt.Workflow feedback (optional)
The cloud agent's GitHub integration could not write upstream Discussions or open the upstream PR (
Resource not accessible by integrationon the one Discussion attempt; no retry). Overlap was checked with read-onlyghsearches and the open-PR title list before the pins were edited.