cache size exposed in Lua API can get out of sync

This is minor nit.

Lua call cache.current_size does not read the cache size from file/LMDB environment so the value reported in Lua can be out-of-sync if another process changed cache size.

The following discussion from !1042 (merged) should be addressed:

  • @pspacek started a discussion: (+1 comment)

    I wonder if cache.current_size returns correct size if some rounding took place inside the backend.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information