UMBRA

History

Kyle Pope be1fdc4551 Calendar backend optimisations: safety caps, shared calendar fix, query consolidation

Phase 1: Recurrence safety — MAX_OCCURRENCES=730 hard cap, adaptive 90-day
horizon for daily events (interval<7), RecurrenceRule cross-field validation,
ID bounds on location_id/calendar_id schemas.

Phase 2: Dashboard correctness — shared calendar events now included in
/dashboard and /upcoming via get_accessible_calendar_ids helper. Project stats
consolidated into single GROUP BY query (saves 1 DB round-trip).

Phase 3: Write performance — bulk db.add_all() for child events, removed
redundant SELECT in this_and_future delete path.

Phase 4: Frontend query efficiency — staleTime: 30_000 on calendar events
query eliminates redundant refetches on mount/view switch. Backend LIMIT 2000
safety guard on events endpoint.

Phase 5: Rate limiting — nginx limit_req zone on /api/events (30r/m) to
prevent DB flooding via recurrence amplification.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-03-15 01:31:48 +08:00

__init__.py

Address all QA review warnings and suggestions for lock screen feature

2026-02-25 18:20:42 +08:00

admin.py

Add user connections, notification centre, and people integration

2026-03-04 02:10:16 +08:00

auth.py

Allow dots in umbral name validation (matches username regex)

2026-03-05 20:30:27 +08:00

calendar_event.py

Calendar backend optimisations: safety caps, shared calendar fix, query consolidation