simonredfern d635ac47ec Fix critical rate limiting bugs: date parameter, hour range, and timezone ... Bug #1: getActiveCallLimitsByConsumerIdAtDate ignored date parameter - Used LocalDateTime.now() instead of provided date parameter - Broke queries for future dates - API endpoint /active-rate-limits/{DATE} was non-functional Bug #2: Hour-based caching caused off-by-minute timing bug - Query truncated to start of hour (12:00:00) - Rate limits created mid-hour (12:01:47) not found - Condition: fromDate <= 12:00:00 failed when fromDate = 12:01:47 Bug #3: Timezone mismatch between system and tests - Code used ZoneId.systemDefault() (CET/CEST) - Tests use ZoneOffset.UTC - Caused hour boundary mismatches Solution: - Use actual date parameter in getActiveCallLimitsByConsumerIdAtDate - Query full hour range (12:00:00 to 12:59:59) instead of point-in-time - Use UTC timezone consistently - Add debug logging for troubleshooting Note: Test still failing - may be cache or transaction timing issue. Further investigation needed. See RATE_LIMITING_BUG_FIX.md for detailed analysis.		2025-12-30 15:01:45 +01:00
..
src	Fix critical rate limiting bugs: date parameter, hour range, and timezone	2025-12-30 15:01:45 +01:00
pom.xml	Drun.mode=test flags --add-opens	2025-12-22 17:24:01 +01:00
web-app_2_3.dtd