Skip to content

fix(read): close integrated pagination and effect-order regressions - #180

Merged
LIghtJUNction merged 9 commits into
integrate/all-open-20260929from
fix/read-page-boundaries-20260929
Sep 29, 2026
Merged

LIghtJUNction merged 9 commits into
integrate/all-open-20260929from
fix/read-page-boundaries-20260929

Conversation

@LIghtJUNction

Copy link
Copy Markdown
Contributor

Scope

Narrow follow-up to #176, based on de3cd872b71e062d6141916b11ea0bdfa28adca6. Only the shared list reader, regression tests and dedicated cloud workflow change. No parallel executor, market or recovery implementation; no writes to the integration branch.

  • Remove artificial empty-string/U+FFFF initial keyset endpoints. First page has no seek condition; subsequent scan batches and cursors use actual SQL keys, preserving order, principal/query/snapshot binding, authorization and budgets.
  • Correct the effect-order test's blanket transaction prohibition: every request still performs the real read-only runtime-generation query; any other SQL or business execution fails the test. Exercise both current and stale generations, GET/HEAD, transaction/external effects, existing/missing/raw/meta/history paths, and full row-value/outbound-effect invariance.
  • Add list/search/read_query@1/@2/@3 pagination coverage with ASCII, CJK and supplementary-plane names, all three sort keys in both directions, exact actual-database ordering, continuous cursors and empty results. Existing signed four-transport matrix remains unchanged.

Refs #78 #82 #83 #85. Does not close broad acceptance or field-evidence issues.

Evidence and notes

Previous exact combined source 9b727c16b893959e358811e543233df1608abb7b, tree 4936af96eb805c4f90aad002008376425a2effa4: full cloud run 36564681470, independently downloaded/provider-SHA256-checked four artifacts, 2407 cases / 6 failures / 0 errors / 0 skips. Four failures are the overly broad effect-test intercept, two the descending signed read matrix.

Current implementation head 12e829a6a7b90c279e9b15cd74cece63978ca387, tree 07449e7ae96399ebcbcd1ae33a53de3d9ab5d8f5. New cloud runs are pending, not yet GREEN. Require the focused workflow, integrated effect suite and full four-shard exact node-ID/conformance/build gates on the final head before serial integration.

Persistent working note: #176 comment 5890775291. The fixed discovery source was prepared by source-only cloud run 36571871534, artifact 11035120921 (ZIP SHA256 02f5421eb68c126198dd1fe0f6936918f339470d9350fa201846a5ed0434d47d); downloaded source exactly matches the reviewed bytes. The auxiliary publisher neither executes project code nor changes a branch and is absent from this product tree. Project execution/tests/builds are cloud-only.

No production deployment, Root/PIN, financial operation, outbound delivery, backup/key destruction or recovery promotion.

…ery effect guards

Use no seek predicate for the initial page and actual cursor keys for continuations. Keep runtime-generation checks real in effect-order regression coverage, with explicit stale-generation rejection. Add PostgreSQL ordering/Unicode pagination and cloud-only regression evidence.

Refs #78 #82 #83 #85
Correct the focused workflow diagnostic without bypassing failures or changing runtime source/test assertions. Preserve verified prior RED evidence and active run references in the existing progress note.
LIghtJUNction added a commit that referenced this pull request Sep 29, 2026
…on fixes

Preserve both regression-first and PR #180 histories. Scan at most 128 rows per query, apply current target visibility per row, enforce a 4096-row/monotonic deadline budget, and return continuation only from a visible lease. Preserve existing v1 output and v2 Resource contracts.

Cloud RED 36573737687: 13 cases, exactly two explicit unbounded SQL failures, no errors/skips. Runtime source SHA256 ac4247f5629403942506a80c895e4018db4ec56d3a2e279a11a6fedbbef3b74d; no unrelated handoff changes.

Refs #81 #85

Copy link
Copy Markdown
Contributor Author

2026-09-29 13:20Z continuation

Pushed the refined read/recovery regression follow-up. Current branch head: f304bcf7d620f7584582d145c41e719140779053.

  • 759ba54a: narrow the HTTP effect-order observer so the real runtime-generation read remains mandatory while business reads/writes/execution stay forbidden.
  • 8e5c9142: add 30 cross-operation/sort/direction keyset regressions using actual PostgreSQL ordering and supplementary-plane names.
  • 6540c796: fold the checks into the existing integration workflow, run PostgreSQL C and en_US.utf8 independently, record source/database evidence, and read locale from pg_database rather than unsupported lc_collate runtime settings.
  • f3258bf3 / f304bcf7: remove the temporary standalone workflow and its superseded compact pagination test so there is one integration gate.

Push-triggered/PR-triggered cloud verification is now queued/pending on the final head. Observed runs include Integration regression closure 36575194515, Rewrite contracts 36575194550, Issue recovery regressions 36575194525, Recovery safety 36575194502, Architecture boundary regressions 36575194487, Storage session boundaries 36575194531, Hosting read-only boundary 36575194503, Client boundary 36575194507, and Credential delivery boundary 36575194458.

No GREEN claim yet; final-head CI remains authoritative. Refs #78 #82 #83 #85.

Copy link
Copy Markdown
Contributor Author

独立回收 f304 双排序规则证据 / 并行边界

已独立下载 run36575194515 的两个 JUnit artifact、核对 provider ZIP SHA256、实际 source.json 和 database.json:

  • C:artifact11038010742,SHA256 1ba09659e4b296473aa83f9c746d795fea1afc4bffc5133c9e602263688dc25e,89项/0失败/0错误/0跳过。
  • en_US.utf8:artifact11037535906,SHA256 9124e9120db01b9ef07f29d02ed56ce7550c6a05043010e5b798bf314d0684a2,89项/0失败/0错误/0跳过。

两者实际测试提交同为9495ad89e96bda9530f93a6dc4a348f09bb328b6,tree5308419e5e2b73d474eee0dfaef7a933876c6896;实际PG16.15的lc_collate分别确为C/en_US.utf8。它们是同一套89用例在两种环境重复执行,不计成178个独立验收要求。全量36575194550尚在执行,不替代完整门禁。

本轮不再修改本分支,保留f304后续测试/CI收敛。#181的legacy lease_list修复仍在独立70d分支,全量36574831146执行中,专项14/14已独立验证;下一步组合必须保留本PR的新测试和集成workflow,不复活已删除的临时分页文件。另在独立工作分支对Resource-backed协作列表无LIMIT做RED复现,范围和笔记见#81评论5891421418,未改本PR或#176。

@LIghtJUNction
LIghtJUNction merged commit bf1a166 into integrate/all-open-20260929 Sep 29, 2026
13 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant