Calendar photo burst can leave items out of the Calendar listing #217

Open
opened 2026-09-27 07:03:09 +00:00 by kayg · 1 comment
Owner

Reproduction

On branch job/search-palette at post-merge commit ae33137bac8a92426f280d857a64365cda3c7266, tests/adversarial/attack.py uploaded 120 tiny JPEGs to one Calendar day with an 8-worker TUS burst.

The run reported NO RESPONSE for eight create/byte-upload requests (burst-106 through burst-113). The subsequent /api/v1/calendar/items scan reported expected 120 burst photos, saw 113. The server stayed alive. Other worktrees and adversarial jobs were active on the shared host, so load may have contributed, but this was a non-SLOW item-count mismatch.

Please determine whether these requests failed to install their files or whether Calendar indexing lagged behind completed uploads. Add a regression check that waits for the expected settled state and verifies all 120 stable item identities are returned without duplicates. The 8-worker TUS burst is in tests/adversarial/attack.py.

## Reproduction On branch `job/search-palette` at post-merge commit `ae33137bac8a92426f280d857a64365cda3c7266`, `tests/adversarial/attack.py` uploaded 120 tiny JPEGs to one Calendar day with an 8-worker TUS burst. The run reported `NO RESPONSE` for eight create/byte-upload requests (`burst-106` through `burst-113`). The subsequent `/api/v1/calendar/items` scan reported `expected 120 burst photos, saw 113`. The server stayed alive. Other worktrees and adversarial jobs were active on the shared host, so load may have contributed, but this was a non-SLOW item-count mismatch. Please determine whether these requests failed to install their files or whether Calendar indexing lagged behind completed uploads. Add a regression check that waits for the expected settled state and verifies all 120 stable item identities are returned without duplicates. The 8-worker TUS burst is in `tests/adversarial/attack.py`.
Author
Owner

Reproduced during the real-server adversarial round for #188 at HEAD 9bd81553. The probe uploaded 120 photos under one Photos/<year>/<date> folder, then paged Calendar items with a page limit of 7. It reported calendar items burst :: expected 120 burst photos, saw 0. The upload requests returned 201/204, though many were SLOW on the shared host. The later Photos shared-root isolation check passed; this finding concerns the existing Calendar photo listing probe.

Reproduced during the real-server adversarial round for #188 at HEAD 9bd81553. The probe uploaded 120 photos under one `Photos/<year>/<date>` folder, then paged Calendar items with a page limit of 7. It reported `calendar items burst :: expected 120 burst photos, saw 0`. The upload requests returned 201/204, though many were SLOW on the shared host. The later Photos shared-root isolation check passed; this finding concerns the existing Calendar photo listing probe.
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#217
No description provided.