Search date filter omits a Journal Log on its logged-zone day #232

Open
opened 2026-09-27 12:22:53 +00:00 by kayg · 0 comments
Owner

Found in the post-merge adversarial run for Forgejo #118 at head c2ff7b40, in tests/adversarial/attack2.py (tz-days).

Reproduction:

  1. Create a Journal Log entry with a unique title, now=2026-08-14T18:29:00Z, timezone=Asia/Kolkata. The API returns 201 and date=2026-08-14.
  2. Search for the unique title with x-calternal-timezone: Asia/Kolkata. The unfiltered Search query returns the Log result at /d/2026-08-14.
  3. Search for the same title plus date:2026-08-14. The API returns 200 but has no Log result.

Expected: the date filter includes the Log entry on its Asia/Kolkata day. DESIGN §30 records that Journal day boundaries follow the zone in which the Log entry was recorded; see also #45. The probe reported this as a non-SLOW finding and the server remained alive.

Found in the post-merge adversarial run for Forgejo #118 at head c2ff7b40, in tests/adversarial/attack2.py (tz-days). Reproduction: 1. Create a Journal Log entry with a unique title, now=2026-08-14T18:29:00Z, timezone=Asia/Kolkata. The API returns 201 and date=2026-08-14. 2. Search for the unique title with x-calternal-timezone: Asia/Kolkata. The unfiltered Search query returns the Log result at /d/2026-08-14. 3. Search for the same title plus date:2026-08-14. The API returns 200 but has no Log result. Expected: the date filter includes the Log entry on its Asia/Kolkata day. DESIGN §30 records that Journal day boundaries follow the zone in which the Log entry was recorded; see also #45. The probe reported this as a non-SLOW finding and the server remained alive.
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#232
No description provided.