fix(cache): make in-memory backend Close-able so Shutdown stops its cleaner

cache.Shutdown only called Close() on an io.Closer, which only the Redis
backend (CacheWrapper) satisfied -- the in-memory Cache's Shutdown
(cancels ctx, stopping its cleanupRoutine background ticker) was never
reached, so that goroutine leaked until process exit (and with the
default set-up, and whenever Redis is unreachable and EnableCache falls
back to memory).

Add Close() error to Cache (calls Shutdown, idempotent, leaves the
cache usable) so cache.Shutdown handles both backends symmetrically.
Update Shutdown doc; add test TestMemoryCacheClose_IdempotentAndStillUsable.
This commit is contained in:
2026-08-13 11:36:52 +01:00
parent d410fb3c7e
commit df2f80f55f
3 changed files with 38 additions and 1 deletions
+1 -1
View File
@@ -169,7 +169,7 @@ func EnableCache(cfg *CacheConfig) {
}
// Shutdown closes the underlying cache client if it owns external resources
// (the Redis connection pool). No-op for in-memory caches.
// (the Redis connection pool, or the in-memory cleanup goroutine).
func Shutdown() {
if config != nil && config.Client != nil {
if closer, ok := config.Client.(io.Closer); ok {