Repository navigation
Read workflow descriptions through one coherent snapshot - #1112
Conversation
Reuse the description connection for memo, command, summary, routing, search, update, failure and projection reads. Share the native start payload with query and definition routing. Force the existing repeatable snapshot primitive even on MySQL/MariaDB READ COMMITTED sessions. Add real concurrent-termination controls, a READ COMMITTED counterexample, one-checkout/start-read counts, and error/cancellation release controls. First compile and execution are deferred to the normal hosted source train. Refs #1075. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-Authored-By: Codex <noreply@openai.com>
|
|
Source qualification PASS on exact head 62success,1intended path-gated skip,0statuses. All6original runs concluded success on attempt1: Shared42575196749, PHPUnit42575196765, Sonar42575196734, CodeQL42575192395, Boundary42575196838/42575191363. Rust initialization/analysis/upload succeeded; the combined source therefore has current Rust analysis. The earlier #1110 actual-main download NONPASS remains a different run, not relabelled. Retained backend artifacts were rehashed against GitHub's archive digests. PostgreSQL16/17 each name The deterministic test forces a real termination to commit between the run-row read and later description reads. It requires a complete pre-transition response, a later terminated response, one checkout/start-payload read, and connection release on not-found, corrupt memo and cancellation. The MySQL/MariaDB test runs both session isolation levels and the ordinary READ COMMITTED mixed-response counterexample before/after the explicit snapshot. Existing routing, legacy projection and DTO suites are green. No benchmark speedup or published-artifact acceptance is inferred. General accepts this source and selects one ordinary queue entry at the exact head, after empty-queue/current-main/mergeability/check rechecks. The expected merge parents are [0b383e5,eb35eef5], treeb86bfa06. Observe up to45min; if still live then, one exact dequeue, no automatic re-entry. Integration/main checks and later patch publication remain required; released3.3.1 is unchanged. |
|
One queue entry accepted at2026-11-09T07:13:12Z, position1, stateQUEUED; exact head eb35eef and empty-queue/main guards passed. Ceiling2026-11-09T07:58:11.413986+00:00. No source push or rerun. Observe the merge group, then signed parents/tree/current-main checks; no release selected by enqueue. |
|
#1112 merged at07:38:46UTC as signed main |
|
Actual-main result on241867ab is terminal NONPASS on managed CodeQL infrastructure, not a full green custody claim. All original product workflows passed: Shared42580646709, PHPUnit42580646550, Sonar42580646552 and Boundary42580646518. Managed run42580645989 attempt1 has Rust/Python/JavaScript success; Actions129038263409 failed Initialize CodeQL on4download attempts for codeql-bundle-actions-linux64.tar.zst with504, before analysis. LogSHA25671862081f8386106e5f8b5f4c0dfad0b6199bdf662d9e6f0456f908519ee7990. The original failed run is retained; no rerun or cancellation. Both source and queue were green, and source head eb35eef already obtained all4CodeQL language analyses on the reviewed tree. The main merge is signed, has ordered parents[0b383e5,eb35eef5] and exact treeb86bfa06; its only missing analysis is the managed Actions download. GitHub's default-setup job retry route is known unsupported from #1110, so it will not be repeated or the configuration altered. General revises the agent-chosen sequencing to allow the already planned, legitimate two-file3.3.2 release-source PR to enter ordinary draft CI from241867ab. This does not call this main green or waive analysis: the release-source candidate and final release commit must obtain normal required/source/security checks before a tag/publication. The version/notes change is needed to deliver #1068/#1075, not an empty retry commit. Both feature topics stay retained while qualification is incomplete. No tag, image, alias or release effect is selected by this decision. |
Workflow descriptions currently assemble run state, commands, memo, routing and diagnostics across separate pool reads. A concurrent transition can leave one response containing different database generations. This change uses the existing repeatable-read primitive and one connection for the complete description, including MySQL/MariaDB sessions configured READ COMMITTED. The native start payload is reused where authority is identical; legacy projection metadata retains its own first-event authority.
Refs #1075. This follows #1068 on main and is excluded from released 3.3.1. No speedup is claimed.
Validation added: pause after the real run row, commit a termination from a separate pool, and require the entire response to equal the earlier snapshot; the next description must show termination and its command. A one-connection reader counts checkouts and the shared start-payload read. Error, corrupt memo and cancellation controls require the connection back. MySQL/MariaDB run both session isolation levels and demonstrate the ordinary READ COMMITTED counterexample before and after the explicit snapshot. PostgreSQL and read-only SQLite WAL readers cover the same transition.
First compile and test execution are this normal hosted train. Only source review, whitespace and bounded privacy checks ran locally. All maintained describe, routing and projection suites remain required. Main's earlier Rust CodeQL bundle-download failure remains recorded on #1110; this candidate must pass normal analysis and all required checks before integration.