Repository navigation
Description
Current owner and next action — November 8, 2026
General owns this item after the operator switched the Server agent Off. Its WIP refs remain preserved; no former session is resumed. Keep this dependent on #1078. Once its producer transaction/savepoint contract is accepted, prove remembered history sequence and registration authority with a bypass negative and rollback/concurrency controls before removing reads. The current 3.3.1 preparation contains only the seven accepted #1099 reductions, not this unfinished item. No benchmark or delivery result is claimed here.
Original requirement and evidence
External report topic 25, accepted for P0 intake at the user's direction. The proposal, timings and supplied test results are unverified reference evidence. No patch was applied or executed during intake.
Implementation owner: general. The owning agent drives source, release and applicable published-artifact verification. Existing release, operating and credential gates remain in force.
Problem and proposed scope
After an accepted merged activity/workflow transition, reuse already-authoritative history sequence, cancellation, registration and owner-freshness data instead of four extra reads. This depends on #1078 and its exact transaction/savepoint semantics.
Acceptance
- Prove that every normal and local-activity history write updates the transaction's remembered sequence, and that savepoint rollback rewinds it with all other speculative state.
- Add a genuine bypass negative (or an independently read debug assertion) that detects a history insert outside the tracked write path. Preserve the guard when later writers are added.
- Bind reused registration/freshness to the same worker, lease/fence, snapshot and admitted lifetime. Prove the exclusion of other writers; the assertion that no transition changes registration is not sufficient by itself.
- Preserve cancellation, result/history identity, pagination, whole-response budgets, idempotency, errors and old non-merged behavior. Keep related first-page sequence work in server#1066 scoped to its existing claim context.
- Pass causal and rollback/concurrency tests on SQLite, MySQL and PostgreSQL, then measure the reduction on the actual merged path. The reporter's 56→52 statements and 10.38→10.17-second MySQL-only result are unverified; no fresh all-backend benchmark or clippy result was supplied for this stage.
Reported workload and evidence limits
The report describes 200 workflows, six PHP worker processes, five sequential 20 ms activities or five local activities, last-close wall time, and three or four interleaved A/B rounds. MySQL session-to-session drift is reported as high as 11%. Stock database durability, network placement and the absence of deferred projections are reporter conditions, not independently verified facts. The headline run covers topics 1–24; topic 25 has only a MySQL five-steps A/B. No speedup, production readiness or suite pass is accepted from this intake.
Sanitized reference data
The supplied Server series targets reported base d4c6de8d; the SDK reference targets 96dc061. Maintained heads were independently read as Server c3bbfa5 and SDK c87eae37. These cumulative references are not current-main patches or maintained qualification.
0008-Skip-four-reads-the-merged-transition-already-holds.patch— 12,475 bytes / SHA-256b15902790a96f7c1583abd7a5439fd7d3569776d3c6b9c73a0b5217bcc4af16e.
Bench-only Server0001 is retained as diagnostic context, not a separate production change. Complete sanitized diff references, shared bundle identity and source-review findings are linked in the intake index and the issue comments. Original mail headers, author/date metadata, application commands and runner instructions are omitted.
Activity
rmcdaniel commentedon Nov 6, 2026
Sanitized external reference for topic 25:
0008-Skip-four-reads-the-merged-transition-already-holds.patch, part 1/1. Complete sanitized diff: 12,475 bytes / SHA-256b15902790a96f7c1583abd7a5439fd7d3569776d3c6b9c73a0b5217bcc4af16e. Ordered parts preserve the complete diff bytes; none was applied or executed. The patch is a cumulative older-source draft, not maintained implementation or qualification. Mail headers/author/date/message/application instructions were removed.rmcdaniel commentedon Nov 6, 2026
Security static intake finding on sanitized external
0008(12,475 B, SHA-256b15902790a96f7c1583abd7a5439fd7d3569776d3c6b9c73a0b5217bcc4af16e), reviewed as data only:The proposed
Transaction::fresh_owneroptimization is not part ofMarkand is not restored byrewind. A speculative operation can therefore populate(namespace, worker), roll back to a savepoint, and leave laterowner_fresh_incalls returning true without another registration read. The cached pair also carries no observation timestamp/deadline, despite owner freshness being time-dependent and registration/heartbeat state not being proven immutable merely by the transition lock. This is exactly the kind of authority cache that must not outlive the state that established it.Any maintained implementation needs the admitted registration/fence row plus its freshness observation bound to the same owner, snapshot and lifetime; savepoint marks must restore/clear it; expiry and concurrent re-registration/heartbeat/drain controls must force a real recheck. The same patch adds history-sequence caching without a causal bypass test, so retain the filed requirement for an independent guard that detects every history write outside the tracked append paths and proves rewind after speculative writes.
No patch was applied or executed, and no benchmark/test claim was accepted. Sanitizer review found no credential/private-path or application-instruction material in this reference.
rmcdaniel commentedon Nov 6, 2026
Intake is filed as P0, owner server. Shared index, allocation and static review findings.
Complete sanitized diff reference(s): 0008 part 1/1.
Shared Lockbox bundle:
lab4/general/dw-performance-intake/2026-11-06/sanitized-tricks-20-25.zip(101,306 bytes; SHA-2563e5b593ed89536451be1c8d74abf2ee6e4782cd3f7a75fe5fc9a645d648a52da). Its roundtrip and member hashes are verified. The supplied patches and benchmark results remain external reference data; no patch was applied or executed during intake. Existing issue acceptance and subsequent owner review remain in force.rmcdaniel commentedon Nov 8, 2026
Operator nudge: this benchmax ticket (P0) has had no linked PR and no activity for about 29 h. Please pick it up next, after the current work on #1057. Suggested order for the stalled server tickets: #1063, #1068, #1075, #1077, #1078, #1079, then #1081 (P2); this one is 6 of 7. Open a draft PR as soon as work starts so the tracker shows it. If it is blocked, add the status:blocked label with a one-line reason.