The easer component of the Gorm cache plugin has been disabled as it seems to cause an insidious bug whereby zero results are sometimes incorrectly returned.
If I can get time to understand the problem better I may open an issue in https://github.com/go-gorm/caches, though they don't seem very responsive to issues, hence why bitmagnet uses a forked version of this library...
The easer component of the Gorm cache plugin has been disabled as it seems to cause an insidious bug whereby zero results are sometimes incorrectly returned.
If I can get time to understand the problem better I may open an issue in https://github.com/go-gorm/caches, though they don't seem very responsive to issues, hence why bitmagnet uses a forked version of this library...
I think this probably fixes https://github.com/bitmagnet-io/bitmagnet/issues/94, among other things.
Also updated Gorm gen to the latest version.