This is similar to
#703, but the resolution for that does not apply to me.
After upgrading to 1.5.1, I found that sometimes the commits were disappearing. vcs_full_cache was True.
This is probably because, the setup regularly (but not most of the time) requires us to commit from outside rhodecode. So, manually invalidating the cache is not an option.
Setting vcs_full_cache to False resolves this issue, but destroys the performance.
Is there a better way to enable caching but invalidate the cache when commits are made from outside.
I've only tested this with 1.5.1 right now, but I'm guessing this might happen with 1.5.2 too.