Merge35 BLOCKER: journal sync PATCH returns 503 and duplicates a paragraph #1474

Open
opened 2026-10-08 13:53:29 +00:00 by kayg · 1 comment
Owner

Merge35 (#1458) real-release journal race reports both HTTP 503 and duplicated sync content. This blocks READY: the owner rule blocks sync collisions and data inconsistency.

Exact findings:

!! journalrace: sync upload: ('patch', 503, b'{"error":{"code":"service_unavailable","message":"Index is busy; retry shortly"}}')
!! journalrace: sync upload: ('patch', 503, b'{"error":{"code":"service_unavailable","message":"Index is busy; retry shortly"}}')
!! journalrace: duplicate line: 2 times: 'sync paragraph 5 from a phone'
!! journalrace: sync line: 'sync paragraph 5 from a phone' appears 2 times
journalrace: 2021-03-14: 6 seeds, 40 creates answered 201, 0 timed out (0 of them landed), 8 uploads, 46 entries

The findings occur in tests/adversarial/attack2.py's journalrace section after the shared-host analytics storm. The 503 and duplicate content are not SLOW-only successful requests. Preserve every old response and uniqueness expectation.

Check whether a source write lands before the Index failure, and whether retry/reconciliation repeats a paragraph without the correct revision/receipt boundary. The causal sequence is not confirmed by the summary alone. Do not treat this as load until the content invariant is explained and protected by a focused regression.

Product build 938a141d5; integration head 0ba15bd945. Local log: artifacts/merge35/adversarial.log. The separate Calendar write 503 is #1469.

Merge35 (#1458) real-release journal race reports both HTTP 503 and duplicated sync content. This blocks READY: the owner rule blocks sync collisions and data inconsistency. Exact findings: ``` !! journalrace: sync upload: ('patch', 503, b'{"error":{"code":"service_unavailable","message":"Index is busy; retry shortly"}}') !! journalrace: sync upload: ('patch', 503, b'{"error":{"code":"service_unavailable","message":"Index is busy; retry shortly"}}') !! journalrace: duplicate line: 2 times: 'sync paragraph 5 from a phone' !! journalrace: sync line: 'sync paragraph 5 from a phone' appears 2 times journalrace: 2021-03-14: 6 seeds, 40 creates answered 201, 0 timed out (0 of them landed), 8 uploads, 46 entries ``` The findings occur in `tests/adversarial/attack2.py`'s journalrace section after the shared-host analytics storm. The 503 and duplicate content are not SLOW-only successful requests. Preserve every old response and uniqueness expectation. Check whether a source write lands before the Index failure, and whether retry/reconciliation repeats a paragraph without the correct revision/receipt boundary. The causal sequence is not confirmed by the summary alone. Do not treat this as load until the content invariant is explained and protected by a focused regression. Product build 938a141d5; integration head 0ba15bd9459c66dd820297474b71d603ca8e637f. Local log: `artifacts/merge35/adversarial.log`. The separate Calendar write 503 is #1469.
Author
Owner

m35triage (#1458): completed the requested focused production-versus-merge comparison. Production is af202e1514; integration keeps all 28 heads and the af202e151 Copy link hotfix. Three complete samples per release ran in alternating order with fresh fixtures and unchanged checks. Both release servers were built locally; sample 1 on production used the pinned shared af202e151 release. The fresh builds use the same web assets to keep the client control constant.

Build Run Journal 5xx Duplicate-line findings Calendar 5xx Follow-up mismatches
production 1 0 0 0 0
production 2 0 0 0 0
production 3 0 0 0 0
merged 1 0 0 0 0
merged 2 0 0 0 0
merged 3 0 0 0 0

Journal sync race did not reproduce its historical failure in this selected scope. No merged-only regression was observed, so the passing oracle does not support a bisect. This does not establish the cause of the earlier combined-load failure; leave this issue open for its fix/investigation job. The prior analytics/general phases were excluded as requested. Accepted Calendar SLOW responses remain recorded, all HTTP 201.

Journal samples each preserved six seed entries and 40 creates that answered 201, with 46 final entries. Every accepted upload paragraph appeared once. Calendar move, destination and delete checks passed. No expectation or fixture was weakened. Incomplete setup/scope-wrapper attempts remain in the audit and are excluded from this six-run table. Logs and machine-readable results: artifacts/m35triage/.

m35triage (#1458): completed the requested focused production-versus-merge comparison. Production is af202e1514955ddf0f8b4b3d2503c780d807ed84; integration keeps all 28 heads and the af202e151 Copy link hotfix. Three complete samples per release ran in alternating order with fresh fixtures and unchanged checks. Both release servers were built locally; sample 1 on production used the pinned shared af202e151 release. The fresh builds use the same web assets to keep the client control constant. | Build | Run | Journal 5xx | Duplicate-line findings | Calendar 5xx | Follow-up mismatches | |---|---:|---:|---:|---:|---:| | production | 1 | 0 | 0 | 0 | 0 | | production | 2 | 0 | 0 | 0 | 0 | | production | 3 | 0 | 0 | 0 | 0 | | merged | 1 | 0 | 0 | 0 | 0 | | merged | 2 | 0 | 0 | 0 | 0 | | merged | 3 | 0 | 0 | 0 | 0 | Journal sync race did not reproduce its historical failure in this selected scope. No merged-only regression was observed, so the passing oracle does not support a bisect. This does not establish the cause of the earlier combined-load failure; leave this issue open for its fix/investigation job. The prior analytics/general phases were excluded as requested. Accepted Calendar SLOW responses remain recorded, all HTTP 201. Journal samples each preserved six seed entries and 40 creates that answered 201, with 46 final entries. Every accepted upload paragraph appeared once. Calendar move, destination and delete checks passed. No expectation or fixture was weakened. Incomplete setup/scope-wrapper attempts remain in the audit and are excluded from this six-run table. Logs and machine-readable results: artifacts/m35triage/.
Commenting is not possible because the repository is archived.
No labels
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal-v0#1474
No description provided.