Tomasz Janiszewski

1. Take a look at test https://github.com/allegro/bigcache/blob/0afcdc40f195c6dcd504eaaccb91ce7e5657bb88/bigcache_test.go#L417-L448 2. Could you elaborate?

duplicates https://github.com/allegro/bigcache/issues/226

https://github.com/allegro/bigcache/issues/148#issuecomment-579364262

Thanks for reporting this. Indeed without minimal reproducible example it's super hard to prepare a fix and ensure it was really fixed.

@JamesSunXX @784909593 Could you try https://github.com/allegro/bigcache/releases/tag/v3.0.2

@Fabianexe Good point. Would you like to contribute a patch? We need to change https://github.com/allegro/bigcache/blob/37b9eb28693b36c88824afefa1dfe1a20826e74b/queue/bytes_queue.go#L60 This may require moving logger to separate package to prevent cycle dependency. This will be...

We already have this interface https://github.com/allegro/bigcache/blob/master/logger.go#L9 That's why we need change config

This is working as expected and was one of the design choices we made to keep it simple. When you remove element it's not removed but marked as removed. When...

I think we can add new callback

@jgheewala wyould you like to create a PR with this change? It should be pretty straight forward