doobidoo/mcp-memory-service v10.13.2

v10.13.2 - Consolidation & Hybrid Storage Bug Fixes

on GitHub

v10.13.2 - Consolidation & Hybrid Storage Bug Fixes

This patch release fixes two classes of bugs that caused the memory consolidation system to fail silently or crash when using the Hybrid storage backend.

Fixed

• HybridMemoryStorage missing StorageProtocol proxy methods (delete_memory, get_memory_connections, get_access_patterns): Without these methods, DreamInspiredConsolidator raised AttributeError during the forgetting phase, silently aborting consolidation when using hybrid storage. Each method now correctly delegates to self.primary (the local SQLite backend).

• Timezone-aware datetime comparison TypeError: The consolidation module used datetime.utcfromtimestamp() throughout, which produces naive (timezone-unaware) datetimes. However, get_access_patterns() returns timezone-aware datetimes, causing TypeError: can't compare offset-naive and offset-aware datetimes to crash quarterly and yearly consolidation runs. Fixed across 6 files:

  • consolidation/base.py — _get_memory_age_days()
  • consolidation/clustering.py — _calculate_average_age()
  • consolidation/forgetting.py — current_time calculation and last_accessed fallback
  • consolidation/decay.py — last_accessed fallback
  • consolidation/consolidator.py — filter_memories_by_age, _generate_recommendations
  • consolidation/compression.py — _calculate_time_span + UTC isoformat normalization (.replace('+00:00', 'Z'))

• Refactored delete_memory() in HybridMemoryStorage: Now delegates to delete() instead of duplicating sync logic, eliminating a potential divergence between the two code paths.

• Added missing datetime import in storage/hybrid.py: Required for the get_access_patterns() return type annotation.

Credits

Original fixes by @VibeCodeChef (Kemal) via PR #471. Review fixes (naive memory.timestamp normalization in base.py, clustering.py, forgetting.py; delete_memory() refactor; missing datetime import) applied during code review.

Upgrade Notes

No breaking changes. Users of the Hybrid storage backend who run memory consolidation should upgrade to ensure the forgetting phase and quarterly/yearly consolidation runs execute correctly.