fix: cap in-memory route and geocode caches at configurable max entries#112
Open
kush-mehra1 wants to merge 1 commit into
Open
fix: cap in-memory route and geocode caches at configurable max entries#112kush-mehra1 wants to merge 1 commit into
kush-mehra1 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
recentRouteCache and recentGeocodeCache were plain Map objects that grew without bound. expired entries were skipped on read but never evicted from memory.
added eviction logic: when cache exceeds CACHE_MAX_ENTRIES (default 200, env-configurable), the oldest entries are removed. eviction runs after every cache write.
Fixes #59
GSSOC 2026 contribution