lukaszraczylo 2c9b0a499f fix(memory, connection): two data-race/counter defects ...

1) connection_pool.go: GetConnectionStats read lastRecoveryAttempt (a
multi-word time.Time) without any lock while checkAndRecover wrote it
under recoveryMutex -> data race on live admin API endpoints. Snapshot it
under recoveryMutex (the writer's lock). Regression test
TestGetConnectionStatsRace drives the read path concurrent with the locked
write under -race.

2) cache/memory memory.go: Cache.Get expired path used an unconditional
Delete + atomic decrement, so concurrent Gets on the same expired entry
each decremented entryCount/memoryUsage -> permanent negative drift. Use
LoadAndDelete-with-guard (as evictOldest/evictToFreeMemory already do) so
only the goroutine that actually removes the entry decrements. Regression
test TestMemoryCacheConcurrentGetOnExpiredEntry_CountersConsistent.

2026-08-13 04:02:29 +01:00

..

memory

fix(memory, connection): two data-race/counter defects

2026-08-13 04:02:29 +01:00

redis

fix(cache/redis): scope Clear to owned keys; drop pointless Info call

2026-08-13 02:03:50 +01:00

cache_additional_test.go

feat(deps)!: migrate from fiber v2 to fiber v3

2026-06-21 13:15:14 +01:00

cache_bench_test.go

Fix the introduced bug where RO endpoint could've been accidentally used. (#17)

2024-06-28 21:48:39 +01:00

cache_coverage_test.go

perf+coverage: optimisation pass + coverage push to ≥70%

2026-04-19 19:49:24 +01:00

cache_suite_test.go

Update cache library, use miniredis for testing, add additional benchmarks. (#14)

2024-06-19 23:10:36 +01:00

cache_test.go

Fix the introduced bug where RO endpoint could've been accidentally used. (#17)

2024-06-28 21:48:39 +01:00

cache.go

feat(deps)!: migrate from fiber v2 to fiber v3

2026-06-21 13:15:14 +01:00