Investigate xuser adversarial folder fixture setup failure #386

Open
opened 2026-09-29 02:47:56 +00:00 by kayg · 1 comment
Owner

During the #373 adversarial run, xuser_matrix.py could not complete fixture setup: Folder creation returned HTTP -1. The probe therefore did not reach its cross-user assertions.

Please reproduce the fixture setup against the current server and determine whether this is a server response failure or an adversarial harness/setup issue. This job did not change folder creation or the xuser probe.

During the #373 adversarial run, `xuser_matrix.py` could not complete fixture setup: Folder creation returned HTTP -1. The probe therefore did not reach its cross-user assertions. Please reproduce the fixture setup against the current server and determine whether this is a server response failure or an adversarial harness/setup issue. This job did not change folder creation or the xuser probe.
Author
Owner

Replayed the cross-User matrix against a fresh real server built from job/sec-batch after merging dev. Folder fixture setup completed (POST /api/v1/files/mkdir returned its expected 204), and the probe continued through 280 classified operations, 129 replays and 455 A-ID versus missing-ID comparisons across B, C, D and anonymous. The earlier HTTP -1 setup failure did not recur. The full API round later hit unrelated mixed-load timeouts in photo and Calendar probes; those are tracked in #387. I am leaving this issue open for the owner/orchestrator to close after review.

Replayed the cross-User matrix against a fresh real server built from job/sec-batch after merging dev. Folder fixture setup completed (POST /api/v1/files/mkdir returned its expected 204), and the probe continued through 280 classified operations, 129 replays and 455 A-ID versus missing-ID comparisons across B, C, D and anonymous. The earlier HTTP -1 setup failure did not recur. The full API round later hit unrelated mixed-load timeouts in photo and Calendar probes; those are tracked in #387. I am leaving this issue open for the owner/orchestrator to close after review.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
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#386
No description provided.