Skip to content

Fix #76: queryEvents() month boundary timezone fix#79

Merged
thedhanawada merged 1 commit intomasterfrom
fix/issue-76-month-boundary-timezone
Mar 5, 2026
Merged

Fix #76: queryEvents() month boundary timezone fix#79
thedhanawada merged 1 commit intomasterfrom
fix/issue-76-month-boundary-timezone

Conversation

@thedhanawada
Copy link
Copy Markdown
Collaborator

Summary

  • Fixes EventStore.queryEvents() missing events at month boundaries in non-UTC timezones
  • The byMonth index is built using each event's own timezone, so events near month boundaries can be indexed in a different month than expected by the query
  • Now checks adjacent months (prev/next) when filtering by month and post-filters candidates by actual date overlap with the requested month period

Test plan

  • Verify events on Jan 31 UTC appear in January queries even when indexed under February (Asia/Tokyo)
  • Verify events spanning month boundaries are returned correctly
  • Verify no regression for standard same-timezone queries

Fixes #76

Generated with Claude Code

…ne boundaries

The byMonth index is built using the event's own timezone, so events near
month boundaries may be indexed in a different month than expected by the
query. Now checks adjacent months and post-filters by actual date overlap.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@thedhanawada thedhanawada merged commit f8b97e5 into master Mar 5, 2026
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

EventStore.queryEvents() misses events at month boundaries in non-UTC timezones

1 participant