🔑 feat: Implement TTL Mgmt. for In-Memory Keyv Stores #5127
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
I implemented in-memory TTL management for the cache when Redis is not used, ensuring expired entries are properly cleared. Additionally, I added a
DEBUG_MEMORY_CACHE
environment variable to enable debugging of the memory cache.The motivation for this was discovering that TTL was not being done for in-memory cache when using Keyv.
getTTLStores
,clearExpiredFromCache
, andclearAllExpiredFromCache
to manage cache TTLs when using in-memory cache.DEBUG_MEMORY_CACHE
is enabled.Change Type
Checklist