Merge35: Calendar move returns 503 after a write storm and follow-ups disagree #1469

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

Merge35 (#1458) real-release general adversarial API round reported a Calendar 5xx and inconsistent follow-up writes. This blocks READY under the owner rule even though the shared host also produces SLOW observations.

Exact findings:

 - calendar Event move :: 503 b'{"error":{"code":"service_unavailable","message":"Calendar Index is busy; retry shortly"}}'
 - calendar Event move :: expected the Event in its destination Calendar, got 503: b'{"error":{"code":"service_unavailable","message":"Calendar Index is busy; retry shortly"}}'
 - calendar Event delete :: expected 204, got 404

These occur after the Calendar write/duplicate concurrency storm in tests/adversarial/attack.py. The server is alive at the phase end. Existing statuses, fixtures and follow-up assertions were preserved. The run does not establish whether source bytes moved before the 503, so inspect the filesystem/Index atomicity and the follow-up identity before classifying this as data loss or as a harmless refusal.

The Calendar drag focused production regression passed earlier, including normal writes, rollback and Undo. The broader real API storm still fails. Product build 938a141d5; integration head 0ba15bd945. Local log: artifacts/merge35/adversarial.log.

Merge35 (#1458) real-release general adversarial API round reported a Calendar 5xx and inconsistent follow-up writes. This blocks READY under the owner rule even though the shared host also produces SLOW observations. Exact findings: ``` - calendar Event move :: 503 b'{"error":{"code":"service_unavailable","message":"Calendar Index is busy; retry shortly"}}' - calendar Event move :: expected the Event in its destination Calendar, got 503: b'{"error":{"code":"service_unavailable","message":"Calendar Index is busy; retry shortly"}}' - calendar Event delete :: expected 204, got 404 ``` These occur after the Calendar write/duplicate concurrency storm in `tests/adversarial/attack.py`. The server is alive at the phase end. Existing statuses, fixtures and follow-up assertions were preserved. The run does not establish whether source bytes moved before the 503, so inspect the filesystem/Index atomicity and the follow-up identity before classifying this as data loss or as a harmless refusal. The Calendar drag focused production regression passed earlier, including normal writes, rollback and Undo. The broader real API storm still fails. Product build 938a141d5; integration head 0ba15bd9459c66dd820297474b71d603ca8e637f. Local log: `artifacts/merge35/adversarial.log`.
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

Calendar write/duplicate storm 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 | Calendar write/duplicate storm 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#1469
No description provided.