Repository navigation
Admit prepared PostgreSQL reads and receipt-backed writes - #145
Merged
Merged
Conversation
easel
changed the base branch from
codex/generated-access-executor-join8
to
main
November 11, 2026 23:54
easel
marked this pull request as ready for review
November 11, 2026 23:54
easel
added a commit
that referenced
this pull request
Nov 12, 2026
…d-ideals/nullability-ideals already do 2b32fe1 ('Assert accessor refusal in both validation entry points', in #144/#145) established that the Rust admission may either throw AdmissionError('Accessor properties are not invoked during admission') or return an invalid result. Apply the same helper to the other tests that pass getters. policy-v2 passes fully; the others move on to later, unrelated assertions and stay quarantined with the new reason. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
easel
added a commit
that referenced
this pull request
Nov 12, 2026
* TEMP: run quarantined Bun files on Linux for triage * ci: separate concurrency group per trigger so a nightly dispatch survives later pushes Co-Authored-By: Claude Sonnet 5.5 <[email protected]> * Regenerate the action-plan producer identity; it was stale on main and failed test:prepare bun run test:prepare (and so the nightly job and the SDK source build) stopped at 'Original action-plan producer identity is stale'. Regenerated with bun scripts/actions-plan-identity.ts. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> * schema-browser: import generateDomainPackLoaderSchema from the V4 root #143 moved the loader schema generator to the Rust-backed root and left src/domain-packs/loader.ts as declarations only, so the static validators build failed with 'Export named generateDomainPackLoaderSchema not found' (tests/domain-packs/schema-browser-embedding.test.ts). The same import scripts/build-domain-pack-loaders.ts uses. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> * tests: accept the AdmissionError refusal for accessor inputs, as field-ideals/nullability-ideals already do 2b32fe1 ('Assert accessor refusal in both validation entry points', in #144/#145) established that the Rust admission may either throw AdmissionError('Accessor properties are not invoked during admission') or return an invalid result. Apply the same helper to the other tests that pass getters. policy-v2 passes fully; the others move on to later, unrelated assertions and stay quarantined with the new reason. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> * known-failures: drop the four files that now pass Co-Authored-By: Claude Sonnet 5.5 <[email protected]> * tests: drop the deleted TypeScript modules from the portable-module lint list tests/actions-manifest.test.ts read src/extensions/actions/{manifests,framed-json}.ts, which #143 deleted when the Rust port took over; the lint now covers the two modules that remain. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> * Classify the quarantined Bun files: known-failures.txt keeps only possible regressions, with reasons - 130 files stay quarantined, each with a one-line reason (a failing assertion or error, tagged with a shared cause). - 8 files move to slow-tests.txt: no assertion failure of their own, they need more time (relationship projection matrices, Arrow IPC, DDD PostgreSQL) or a prepared environment (WASM package, action prerequisites). - 6 files were fixed or already pass (see the previous commits). - Remove the temporary triage step from the ts job. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> * nightly: build the WASM package first, install Chromium and Go early, skip the known rdf_parity case; drop four dead evidence allocations The nightly job stopped at test:prepare ('Could not resolve bindings/core/wasm/pkg/umf_core_wasm.js'). The same job then runs build:reference, which needed Go and failed on four evidence-map allocations whose records phase 1 deleted (uuid, typed-reporting, typed-sdk, actions-certificate: those operations now have no recorded evidence). cargo test --workspace skips the single known-failing rdf_parity case. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> * docs: refresh the generated source excerpts of the Actions guide The nightly job's build:docs step refuses stale excerpts; refreshed with bun scripts/actions-docs/build.ts --refresh (the example imports from src/index-node-v4, the V4 root since #143; the public-types list follows the current exports). Co-Authored-By: Claude Sonnet 5.5 <[email protected]> * nightly: every suite runs even if an earlier one failed; Actions guide: no links to deleted evidence - build:docs failed on 'Missing repository link ../../evidence/...' in support-and-evidence.md. The page cited qualification counts from the deleted evidence; it now states what CI tests and points at known-failures.txt. Dead links to removed files in the guide pages became plain text. - The nightly job's suites (Bun, quarantined Bun, browsers, SDK package, cargo test) run with !cancelled(), so one failing suite no longer hides the others. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> * slow-tests: policy-v2 passes but one test takes 132 s on the PR job's addon (120 s limit) Co-Authored-By: Claude Sonnet 5.5 <[email protected]> * nightly: 360 min limit, quarantined files in their own sharded job, workflow_call guard The last nightly run got through setup, WASM, test:prepare, typecheck and the reference/guide build (first time), then hit the 150 min limit inside the full Bun inventory. The inventory keeps its single job with a 6 h limit; the quarantined files (informational) run as four parallel shards from the cached addon. The workflow_call trigger and the github.workflow guard are the same lines release.yml's pull request adds, so the two merge cleanly. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> --------- Co-authored-by: Claude Sonnet 5.5 <[email protected]>
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.
Stacked on #144. Adds the generated PostgreSQL binding and the builder for digest-pinned single-row writes. The selected data lease uses read-only repeatable read and rechecks installation and principal scope. Writes and receipt observation retain the existing UMF table writer, transaction lifecycle, and Rust-backed effect receipts.
The focused UMF suites passed 87 tests and 120 subtests, including the receipt suite. The Python ownership checker reports zero violations, and the receipt suite also passed against the installed Access wheel.
A clean, resolved wheel environment ran the compiled Relay task board on PostgreSQL 18.6. Chromium verified pagination, Node refetch, batched assignee expansion with row-policy filtering, and recovery of the same committed receipt after HTTP response loss. The verification used newly built PR wheels and the qualified local Weft and codegen issuer wheels.
Downstream: DocumentDrivenDX/lintel#3 and DocumentDrivenDX/batten#6.