Investigate Calendar photo and recurring Log probe mismatches #347

Open
opened 2026-09-28 13:47:08 +00:00 by kayg · 1 comment
Owner

Evidence

The one local adversarial run reported these Calendar consistency results under heavy shared-host load:

  • After the photo-burst fixture returned successful upload responses, the Calendar items page returned HTTP 200 but contained 0 of the 120 expected items.
  • A recurring Log occurrence write timed out. The later occurrence-identity check then found one Event identity where the probe expected a distinct entry.

The second observation follows a timed-out request, so the server may have committed it after the client deadline. Reproduce both cases without the shared load before assigning a cause. Keep existing probe expectations unchanged. Add deterministic regressions for any confirmed application defect.

See the report on cross-User audit #331.

## Evidence The one local adversarial run reported these Calendar consistency results under heavy shared-host load: - After the photo-burst fixture returned successful upload responses, the Calendar items page returned HTTP 200 but contained 0 of the 120 expected items. - A recurring Log occurrence write timed out. The later occurrence-identity check then found one Event identity where the probe expected a distinct entry. The second observation follows a timed-out request, so the server may have committed it after the client deadline. Reproduce both cases without the shared load before assigning a cause. Keep existing probe expectations unchanged. Add deterministic regressions for any confirmed application defect. See the report on cross-User audit #331.
Author
Owner

This adversarial round reproduced both findings already recorded here: after the photo-burst setup, the Calendar items probe expected 120 items and saw 0; and a recurring Log occurrence write timed out, after which the identity check found one Event identity where the probe expected distinct identities. The timeout means a late server commit remains possible, and shared-host load prevents assigning a cause. Existing probe expectations were left unchanged.

This adversarial round reproduced both findings already recorded here: after the photo-burst setup, the Calendar items probe expected 120 items and saw 0; and a recurring Log occurrence write timed out, after which the identity check found one Event identity where the probe expected distinct identities. The timeout means a late server commit remains possible, and shared-host load prevents assigning a cause. Existing probe expectations were left unchanged.
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#347
No description provided.