exchange-data-manager/src/exchange_data_manager/cache
rob 958168b3c9 Fix stale data served for limit-only requests
Add freshness check to _detect_gaps() in all cache layers (memory,
database, async_database). For limit-only requests (no start/end),
verify the most recent candle is within 2 intervals of current time.
If stale, flag as a gap so fresh data is fetched from exchange.

This fixes the issue where EDM served hours-old cached data instead
of fetching current candles when clients requested "latest N candles".

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-03-03 14:34:31 -04:00
..
__init__.py Implement M1, M2, M3 milestones - full exchange data manager 2026-03-03 04:05:30 -04:00
async_database.py Fix stale data served for limit-only requests 2026-03-03 14:34:31 -04:00
completeness.py Implement M1, M2, M3 milestones - full exchange data manager 2026-03-03 04:05:30 -04:00
connection_pool.py Implement M1, M2, M3 milestones - full exchange data manager 2026-03-03 04:05:30 -04:00
database.py Fix stale data served for limit-only requests 2026-03-03 14:34:31 -04:00
gap_filler.py Implement M1, M2, M3 milestones - full exchange data manager 2026-03-03 04:05:30 -04:00
gaps.py Implement M1, M2, M3 milestones - full exchange data manager 2026-03-03 04:05:30 -04:00
manager.py Add session-scoped connectors and request metrics tracking 2026-03-03 14:02:56 -04:00
memory.py Fix stale data served for limit-only requests 2026-03-03 14:34:31 -04:00